Frequently asked questions

The home where apps get published, hand-written or AI-assisted. Every file in the catalog ships with a signed identity report: what it is, its exact SHA-256 hash and where it comes from.

We're not a store that judges: we're a catalog that gives you verifiable facts so you can decide.

Publishing is free, and free apps pay no commission of any kind. Today every app in the catalog is a free download.

Fulgeon also sells its own products (like Nítido) with a checkout and PayPal; there, the price you see before paying is decided by the server, not a number baked into the page.

Eight types: apps, bots, games, command-line tools, libraries/SDKs, game mods, plugins/extensions and themes/templates. Each type has its own categories (a game gets genres, not 'Finance').

And every file declares where it runs: macOS, Windows, Linux, web browser, Chrome, Firefox, VS Code, Obsidian, WordPress, Minecraft (Java) — with its loader (Fabric, Paper…) and concrete versions — Telegram or Discord (bots aren't downloaded: they open from a link).

Because your listing is a door from search engines across half the world. The whole catalog works in English, Spanish, Chinese, Arabic, Portuguese and French; switch languages from the footer of any page.

It means Fulgeon signed, with its Ed25519 key, a set of facts about one specific file: name, size, SHA-256 hash, which app and version it belongs to, and when it was registered.

It does NOT mean the app is safe. There's no antivirus or code review behind it: the report doesn't judge what the program does. It states which file this is, so nobody can swap it later without it showing.

No account needed, and no need to trust us: paste the report and its signature into the verify page, or check the signature yourself with the public key we publish over the API. If a single byte of the file changes, the hash no longer matches.

Because the classic attack is publishing something clean, earning downloads, then swapping the binary without changing the version number. On Fulgeon a published version is immutable: new content goes in a new version, and mistakes get withdrawn with a stated reason, leaving a record.

Releases is storage; Fulgeon is a catalog. Here versions are immutable (on Releases you can replace a tag's binary and nobody notices), every file carries a verifiable signed report, the target is data (OS, architecture, loader, versions) and the listing exists to get you found: categories, screenshots, search and six languages.

No. Browsing and downloading are open. An account is for the rest: reviewing, voting, talking to authors and publishing your own work.

Reviews: only people who downloaded the app with their account — the download is recorded and checked first. That's the rule against manufactured reviews. Voting (up or down) only requires an account — and you can't vote for your own app.

A voluntary declaration by the author: part of the code came from an AI. On Fulgeon declaring it costs you nothing — this is exactly the place to publish it with pride. The badge exists so you have the fact.

Use 'Report' on the listing itself, signed in, with the reason. It doesn't fall into a dead mailbox: it's recorded, reviewed, and if a takedown is due it happens with a record of who, when and why.

Through Fulgeon's chat: 'Contact the author' on the listing or 'Send message' on their profile. Nobody's email leaves the platform; if they're away, they get at most one email notice per conversation a day.

Four steps, and the first takes a minute: create the listing (name, pitch, type), upload a version with its file or link, Fulgeon signs its report automatically, and you hit publish. Before publishing you need a verified email and to have accepted the platform terms.

Change it: never. Delete it: no — you withdraw it, from your panel, stating the reason. The version stops being offered but its record and signed report remain — if it could be deleted, so could the proof it existed.

Drafts can be fully deleted, files included, as long as they're unpublished.

Two things: the exact mechanics of security bugs you fix (release notes are also read by people who haven't updated yet) and the internals of your licensing. 'Fixed a security bug on paste' helps; the exploit recipe doesn't.

Yes, three ways: the official CLI (npm i -g @fulgeon/cli), the publishing API with keys, and the GitHub Action so each release in your repo publishes itself. For Minecraft mods, the target takes concrete versions: --target minecraft-java:any:[email protected],1.21.3.

If your app is built on Electron, yes and with zero code: Fulgeon serves the feed electron-updater already understands, for every version you publish. For anything else, there's a public JSON manifest with each app's latest version.

The key can't be recovered: we store its hash, not the key, and it's shown exactly once. Revoke it from your panel — the next request with it gets a 401 — and create another. If it leaked, revoke first, then check for versions you don't recognize.

It's a checkbox when creating the listing, and ticking it costs you nothing: not ranking, not visibility, not treatment. The declaration exists because the fact matters to downloaders, not to filter you out.

Check spam, and if it's not there, request another from your panel with 'Resend verification'. Unverified you can sign in, browse and prepare listings; the only things you can't do are publish them or write in chat.

Recover it: 'Forgot my password' on the sign-in screen; you'll get a link that expires in one hour. Change it while signed in: from your profile, with your current password at hand. Passwords are stored with a modern hash (Argon2id), never in plain text.

The minimum that makes an account work: your email, your public name and what you choose to publish (listings, reviews, messages). The less we store, the less there is to protect. And you can close your account whenever you want: the procedure, step by step, is in the privacy policy.

Yes, from the conversation itself. The blocked person isn't notified: their messages simply stop reaching you, with nothing to argue about. Unblocking is a button too.

With PayPal, from the 'Buy' button on the listing. The final amount is always decided by the server when the order is created — what the page shows is informative — and the button says what the law requires: 'Order with obligation to pay'.

Download is immediate after payment. For that, before paying you tick the box consenting to immediate delivery of the digital content and accepting that this waives your withdrawal right — that's the digital-content rule in consumer law, confirmed to you by email along with your purchase.

That email isn't decoration: it's the third condition the law sets. If it never reaches you, the waiver doesn't hold and you keep your 14 days — check spam and, if it's not there, write to us.

Waiving withdrawal is not waiving a working product. You have the legal conformity guarantee: two years from delivery to claim if the program doesn't do what it says, and during the first year you don't have to prove the defect was there from the start.

The order the law sets: first we fix it; if that fails, a price reduction or termination with a full refund. Write to us by replying to your purchase email.

It's a cryptographically signed key you activate on your machines, with the seat count and terms each product states. The app can check it offline for days: it doesn't phone home every time you open it.

Yes: after paying you get a confirmation email with your license and the link to your receipt and downloads. Keep it — it's your proof of purchase.