Apollon Host
Authorise

Frequently Asked Questions

Press Authorise and sign in with Discord. That is the whole process: no invites, no waiting list, no payment, and no password to forget.
We are open to everyone. If you want to help with server costs anyway, that is entirely voluntary and buys you nothing but our thanks.
Support us

We ask Discord for the identify scope only. That gives us your account ID, username, display name, and avatar, and nothing else.
We never see your email address, your servers, your friends, or your messages, and we do not keep the Discord token after the sign-in finishes.

Permanest is an official domain that never expires. It is paid for by donations and the team, so those links stay up.

Yes. Donate a domain and open a Discord ticket, and we set it up for uploading on your hostname.

There is no hard file-count cap. Each file is capped at 25 MB in this prototype. There is no total-size cap, but abuse gets you banned. This is a screenshot-sharing host, not bulk file storage.

Apollon Host is a division of Apollon AI Research. Contact is through Discord once the server link is public. We are not affiliated with any snack brand.

Owner / Admin / Mod / Plus user. Mod and Admin applications go through Discord. Plus is the paid member rank.

Rotial is a sister tooling name in this mock. Apollon Host is the file host; you do not need Rotial to upload or share.

Turbo is a mock Discord-boost perk: while you boost, you keep Turbo extras (animated avatar, custom file-page colour, priority support). Billing is not wired yet.

Discord sign-in is live. Next is a personal gallery of your uploads, account settings, ShareX / CLI, and a Polish version of the site. The visual map is below. Nothing on it is a promise, and priorities may shift.

Roadmap

Here's where we're heading. Nothing is guaranteed, and priorities may shift. Got a better idea? Tell us.
Now
Planned
Maybe

  1. Account settings

    A settings page worth the name: see what we hold about you, export it, and delete your account along with every file it owns. The privacy policy already promises this, so it should not stay a manual request for long.

  2. Abuse handling

    Uploads and file URLs are rate limited, but the report form still goes nowhere. Reports get a queue behind them, so a file can actually be taken down and an account can be stopped from uploading again.

  3. ShareX & CLI

    Screenshot to URL in one keystroke. Download a ShareX config, or apollon upload shot.png / curl with an API token. The HTTP API is the product; the CLI is a thin client over it.

  4. Real numbers

    The statistics row and the leaderboard are hard-coded placeholders today. They get real endpoints counting real uploads, storage, and views, and every mock table leaves the codebase with them. A fake leaderboard is worse than none.

  5. Polish & translations

    The site is English only. Translations, a language switcher, and localised dates and file sizes come next, with Polish as the first language after English. Legal pages get translated too, not just the buttons.

  6. One EU rulebook

    The privacy policy, terms, and cookie wording are drifting apart. They get consolidated into one reviewed set covering the GDPR, the Digital Services Act, and the EU AI Act, including what our parent company may and may not do with anything you upload.

  7. Custom domains

    Extra hostnames for your links, including Permanest-style domains we keep paid. The FAQ already offers this, but per-user domain routing does not exist yet.

  8. Client-side encryption

    Encrypt in the browser before upload so we only store ciphertext. The key would live in the URL fragment (#key) and never hit the network. Hard to mix with ShareX previews and abuse scanning.

  9. Burn-after-reading

    A file that deletes itself after the first view. Better than an expiry date for one-shot dumps. Still thinking about how this plays with Discord embeds, which fetch the bytes more than once.

  10. Metadata scrubbing

    Strip EXIF, GPS, and author tags from images and documents before they hit storage. Fits the EU / GDPR stance on the site better than keeping camera coordinates in a “private” screenshot.