EVOLVETECH

Open source · Local first · Apache 2.0

Run a piece
of the commons.

A small app can live in many places. Verify its release, host a copy, and support the people who keep it available.

Loading the example release…
Release—
Public assets—
App size—
App backends—

01 / Trust the release

Not verified

A portable application

Public files and a signed manifest, ready to move together.

Release SHA-256
—
Publisher key fingerprint
—
Inspect the public assets
    Verify your own release

    Verification checks the bundle against this key. Obtain the key independently. An untrusted page can replace its own verifier; use the local CLI for independent verification. Uploaded files stay in your browser and are never executed here.

    02 / More than one home

    Choose where it runs.

    Checks contact the listed operators and compare their reported release metadata. They do not attest to remote HTML. The two published example copies are operated by EvolveTech; community participation is open.

    Know what travels

    Public app. Explicit dependencies.

    Mirrors distribute public files. A private API, mailbox or database needs its own operator and recovery plan. The support flow reads a public Algorand indexer and opens your own wallet.

    03 / Bring your own machine

    Your copy.
    Your choice of host.

    Node 22.18+ verifies the signed files before serving them. Activation preserves a previous release for rollback.

    First clone the repository, run npm ci and npm run build. Put the downloaded release and an independently trusted public key in that directory. Local serving binds to 127.0.0.1:4198. Public operators configure their own HTTPS proxy.

    Read the complete quickstart →

    04 / Keep it going

    Support is optional.
    Recipients are visible.

    Choose who to support and the amount for each. Fairground’s payment rail opens your wallet; funds go straight to recipients.

    Set up your wallet, step by step ↗

    Native USDC on Algorand, using your external wallet. Network fees apply. No automatic charge, custody, card checkout or promised hosting reward. Each recipient must be able to receive USDC before links are prepared.

    Open the shared Fairground support flow ↗

    Small footprint. Shared support.

    No required central app server for static releases. Publishers can use existing machines or free-tier capacity. Operators contribute bandwidth, storage, power and care; domains and optional providers still cost money. Donations are voluntary support.