Same app · five clouds · one order

Every cloud prints you a to-do list. Ours prints a link.

We sent the same order to each one: put budget-tracker online for three teammates. Each ticket shows what you get out of the box, and what you’d still have to build or wire yourself.

  • ADD-ONsign up for another service
  • PARTLYsome setup by hand
  • YOU BUILDwrite it yourself
  1. CohostlyTICKET 001 · BUDGET-TRACKER
    YOU GET9 OF 9
    • Deploy from your laptop
    • No repo or config needed
    • Know who is signed in
    • Save data
    • Call AI, no keys in code
    • Connect Google, Slack…
    • Run on a schedule
    • Choose who can open it
    • Run lots of tiny apps
    YOU BUILD0 OF 9

    Nothing. Drop the folder, confirm, share.

  2. VercelTICKET 002 · BUDGET-TRACKER
    YOU GET6 OF 9
    • Deploy from your laptop
    • Call AI, no keys in code
    • Connect Google, Slack…
    • Run on a schedule
    • Choose who can open it
    • Run lots of tiny apps
    YOU BUILD3 OF 9
    • No repo or config neededPartlyCLI works; Git projects are the common path
    • Know who is signed inAdd-onAuth providers from the marketplace
    • Save dataAdd-onDatabases from the marketplace
  3. NetlifyTICKET 003 · BUDGET-TRACKER
    YOU GET8 OF 9
    • Deploy from your laptop
    • No repo or config needed
    • Know who is signed in
    • Save data
    • Call AI, no keys in code
    • Run on a schedule
    • Choose who can open it
    • Run lots of tiny apps
    YOU BUILD1 OF 9
    • Connect Google, Slack…You build itBuild OAuth flows yourself
  4. Cloudflare WorkersTICKET 004 · BUDGET-TRACKER
    YOU GET7 OF 9
    • Deploy from your laptop
    • Know who is signed in
    • Save data
    • Call AI, no keys in code
    • Run on a schedule
    • Choose who can open it
    • Run lots of tiny apps
    YOU BUILD2 OF 9
    • No repo or config neededPartlyDriven by a wrangler config file
    • Connect Google, Slack…You build itBuild OAuth flows yourself
  5. RailwayTICKET 005 · BUDGET-TRACKER
    YOU GET6 OF 9
    • Deploy from your laptop
    • No repo or config needed
    • Save data
    • Run on a schedule
    • Choose who can open it
    • Run lots of tiny apps
    YOU BUILD3 OF 9
    • Know who is signed inYou build itAdd your own auth
    • Call AI, no keys in codeYou build itBring your provider keys
    • Connect Google, Slack…You build itBuild OAuth flows yourself

Tallied from each cloud’s defaults

Our ticket, unfolded

What “nothing left” actually covers.

COHOSTLY · ITEMIZEDBUDGET-TRACKER · SHARED WITH 3
  • Instead of Terminal commandsDrop a folder

    A folder, .zip or GitHub repo. Or ask your AI to send it.

    INCLUDED
  • Instead of A settings mazeConfirm, don’t configure

    We draft the settings from your code. You confirm.

    INCLUDED
  • Instead of Sending screenshotsSend a link

    Share by email, like a Google Doc. Five levels, up to public.

    INCLUDED
  • Instead of Building a login pageSign-in, handled

    Your app knows who’s there. Details only with consent.

    INCLUDED
  • Instead of Pasting API keysAI with no keys

    No key in your code. Spending is capped.

    INCLUDED
  • Instead of Sharing passwordsConnect Google or Slack

    Each person links their own account, one permission at a time.

    INCLUDED
  • Instead of Surprise changesYou approve updates

    Other people’s changes wait for your OK.

    INCLUDED
  • Instead of A server per appMany apps, one home

    Data and schedules built in. Idle apps rest.

    INCLUDED
THINGS TO WIRE0

* If a deploy does stop, you see why in plain words, plus a ready prompt for your AI with the whole log. If a setting is the fix, one button applies it.

Our mission

Small software shouldn’t need a cloud stack.

Bring working code from your machine and get something you can share safely with exactly the people you pick, in one click.

In practice: no terminal, no settings maze, no passwords or keys in your code.

Deploy your first app