Skip to main content

Showcase · overview

What has been built on Alodai.

One card per real deployment: what it is, which parts of Alodai it uses, where its picture came from, and what it does not show.

Every card here is a deployment Alodai owns. A client's platform appears after they have agreed in writing; without that, it is reduced to a description or left off the page.

Showcase · our own products

Built and run by us.

Alodai owns each of these, so there is no third party to ask.

  • app.tribenture.com/world-quest
    World Quest

    Founder capture · Captured

    World Quest

    A walking quest through real cities: the actual map, a narrated guide, a question you can get wrong, and a passport that remembers where you have been.

    Its own domain, the travel experience pack, and World Quest as a project block on the shared platform.

    Stage
    Run
    Domains
    Digital
    Limitation
    Captured from production by the founder.
    app.tribenture.com
  • music-kernel.site.alodai.com/
    Music Kernel

    Seeded demo · Captured

    Music Kernel

    The first site published through Sites — a public page for a deterministic music engine, built from eight blocks of the shipping set with a theme of its own.

    A public site with no app to deploy: publish, and it is live.

    Stage
    Launch
    Domains
    Digital
    Alodai parts used
    Limitation
    The screenshot is a local render of the page's published content, not a capture of the live host.
    music-kernel.site.alodai.com
  • nido.site.alodai.com/
    Nido

    Public page · Captured

    Nido

    The public site of Nido, an IVF companion in private beta in Spain, published in Spanish.

    A public site brought into Sites from a design export and published from there, with no app to deploy.

    Stage
    Launch
    Domains
    Digital
    Alodai parts used
    Limitation
    Shows the public landing page only, in Spanish only; the phone screen in it is the page's own illustration, not the app.
    nido.site.alodai.com

Showcase · client work

Built for clients.

Named only with the client's written agreement. Without it, a description with no name, logo, address or picture.

No client platform is shown here. One appears after the client has agreed in writing.

Showcase · lab

Built to learn from.

Sites made to test the factory, shown only when they are public and ours to show.

No lab site is shown here.

Showcase · more of it

More of World Quest.

More screens from the same product.

  • app.tribenture.com/world-quest/expeditions
    the expedition roster
  • app.tribenture.com/world-quest/expeditions/barcelona
    one expedition, its stops as cards
  • app.tribenture.com/world-quest/expeditions/barcelona
    the same expedition on the street map, one stop open
  • app.tribenture.com/world-quest/expeditions/cartagena
    a stop guide open, with its narration playing

Showcase · how a card gets here

Three things have to be true.

An entry appears when it can carry all three. Not two.

  • Permission, or ownership

    Everything shown today is ours to publish. A client's name and logo go on this page after they have agreed in writing, and not before. Where a client would rather not be named, the entry becomes an anonymised card: a description, with no name, logo, address or picture.

    no logo without consent

  • A screenshot with an origin

    Every image is either captured by a script, from a development stack or from a public page, or taken by hand on a product we own — and the manifest records which, on which host, and when. No customer's data is ever photographed, and nothing here is a mock-up standing in for a product.

    scripts/shots.ts

  • A sentence somebody measured

    Each card gets one sentence about what the deployment is, one about what it has switched on, and one about what its picture does not show. Each has to be checkable against the running product rather than written to sound impressive, which rules out most of the sentences that would fit here.

    no invented metrics

The ledger behind those sentences is in the repository, one row per claim, and it names the file or the test that makes each one true.

Showcase · next step

Yours could be the next one.

Tell us what the platform has to do and who it is for.

Request a platform