Apps you can own

Remember when software was a thing you had? You installed it, it worked, and it didn’t change under you on a Tuesday.

Fungi Apps work a bit like that, with modern plumbing.

Small Apps, from a git commit

A Fungi App is small on purpose: a page, maybe a backend, a little database of its own. You keep its source in git. When you build it, Fungi takes one exact commit and turns it into a Release.

A Release never changes. Every file in it is checked by its fingerprint before it’s installed. If you want something new, you make a new commit and a new Release. You choose which Release is live, and you can go back. Swapping Releases keeps the App’s data.

Installing is not trusting

An App says up front what it wants: your files, a terminal, git, an Agent, image generation. Installing it gives it none of that. The first time it needs something, it asks, and you can say no, or change your mind later.

Each App’s page runs in a sandboxed frame on its own domain. Its backend gets only the access it declared, checked again on every request. Even the Apps we ship, Grove, Inkcap and Prints, play by these rules. Don’t like our inbox? Fork it, or pick another one.

Where Apps live

A small story

Mae runs a pottery studio. She forks Inkcap, the file editor, so it shows her glaze recipes as cards. She builds it, previews it, accepts it. A month later she tries a change she doesn’t like, and switches back to last month’s Release with two clicks. The recipes are still there.

Then she lists “Glaze Cards” in the Bazaar for $4. Another studio buys it. They get that exact Release, and it asks them for its own permissions.

Honest limits

Try it now, no account needed:

npx @fungi.computer/oyster try

Try Oyster · Find, install and sell Apps