The zero-setup cloud for small software

Everything your AI-built tools need. None of the setup.

Bring working code straight from your machine. Cohostly makes small tools usable with hosting, authentication, data, AI, OAuth integrations, and access controls—without stitching together a cloud stack.

Deploy your first app

No mandatory Git repository. No deployment config maze.See how it works

I. The part nobody wants to build

The code was the easy part.

Claude Code, Cursor or Codex can get a useful tool working in an afternoon. Then comes everything that makes it usable by someone else.

II. The usual way

You wanted to ship software. Not become its infrastructure team.

9 chores, hung out to dry. Again for every app.

III. From local to live

Works on your machine? Good. Start there.

“Build me a budget tracker.”

i.

Build it your way

Claude Code, Cursor, Codex or your usual editor. Run it until it works.

$ platform deploy

ii.

Snapshot the folder

It packs the project as it is and works out the runtime, start command and port.

budget-tracker.cohostly.cloud

iii.

Deploy it

Check the settings, say yes, and get an app URL.

Shared with 3

iv.

Add what it needs

Turn on sign-in, data, AI and integrations, then share it by email.

No terminal? Upload the folder, connect GitHub, or ask your assistant over MCP.

ONE COMMAND

Your folder, as it is.

platform deploy packs the project you already ran (leaving out node_modules and .git) and works out how to start it. You see the settings before anything goes live. Try it.

budget-tracker01 / DEPLOY

There is no manifest, so here are the settings worked out from your code.

runtimenodehigh
startnpm starthigh
port3000medium

Example settings. Yours come from your code, and you can edit them first.

Nothing deployed yet

IV. More than a place to host

Your app deserves more than a URL.

Built in, and built to work together: sign-in knows who is calling, connections use their consent, approvals ask the right owner.

$ platform deploy[4/4] Livev1budget-tracker

i.Local deploys

From your folder, as it is.

Priyasigned inName, emailif she agreesNo login screen to build

ii.Sign-in

It knows who is calling.

TEAMSPENTMarketing$12,400Engineering$38,900Events$4,150

iii.Saved data

A database for each app.

Summarise this weekSpend is up 8%, mostly Events.spend cappedno key needed

iv.AI built in

Models with no key in code.

Google SheetsreadOutlookmail onlyApps never see a token

v.Managed OAuth

Accounts linked once.

MTWTFSSWeekly reportMon 8:00

vi.Schedules

Runs while the app rests.

PriyaAdminDanEditorMayaViewer

vii.Access

From public to private.

Take a lookSend to 6 people?DenyApprove

viii.Your OK first

Risky steps wait for a yes.

LogseditorsRun a scheduleeditorsShip a versionadmins

ix.No repo needed

Look after it by role.

v3livenowv2Roll backv1Mon

x.Undo

Every version kept.

TWO · CONNECTED

Let your tools do more than sit in a browser tab.

Managed OAuth, AI bindings and schedules mean the integration work is done once, by the platform. Reading someone’s data and acting for them are separate permissions, and acting waits for a yes. Try it.

weekly-report02 / CONNECTED

May I send this week’s summary to 6 people?

Every Monday at 8:00scheduleRead “Q4 Budget”reads · Priya agreedSummarise the changesAI · no keyDraft it in Outlookacts · needs a yes

Sheets and Outlook are separate connections with separate permissions. The app never holds a token.

Waiting for Priya

THREE · NO KEYS

Your users never bring an API key.

An AI resume editor, shared by link. People sign in and use it. Nobody clones the code or pastes a provider key, because the app calls models through Cohostly and you set the spending cap.

resume-editor03 / AI

Tighten this bullet.

Was responsible for helping with the migration of several internal systems.Led the migration of 4 internal systems to one platform, ahead of schedule.
await platform.ai.messages({ model, messages, }) // no provider key in the app
No key asked of anyonespend capped

FOUR · ACCESS

Share the app. Not the repository.

Every app gets its own address. Pick who can open it. The app knows who each person is, and only sees a name or email if they agree. People who use it and people who look after it get different roles.

budget-tracker04 / ACCESS

Who can open it?

People in your account can open it.

YOUR TEAMROLE
Maya · uses itViewer
Dan · logs, schedulesEditor
Priya · sharing, shippingAdmin
Everyone in your account gets in, each with their own role.
Nobody needs the repo to use itplatform share

VI. The cloud, rethought for small software

Most clouds help you deploy. Cohostly helps your little apps work.

ROUTE A · THE USUAL WAY

Eight stops.

Rewired for every app.

Repository
Build config
Auth provider
Database
OAuth app
AI keys
Cron jobs
Access rules
Steps vary by platform8 services to wire

ROUTE B · COHOSTLY

Four stops.

The same every time.

i.platform deploy
ii.Confirm settings
iii.Turn on what it needs
iv.Share it
live
budget-tracker · shared with 3

VII. Platform by platform

Every cloud can host code. Here’s what you set up yourself.

Each row is something a small app needs. Each box says how you get it on that platform.

KEYBuilt inready to useAdd-onfrom a partnerPartlypossible, not the defaultYou build ityour code, your upkeep
WHAT THE APP NEEDS
YOU ARE HERECohostly9 of 9 built in
Vercel6 of 9 built in
Netlify8 of 9 built in
Cloudflare Workers7 of 9 built in
Railway6 of 9 built in

DETAILS · TAP A ROW

Connect Google, Slack…

Tokens held, refreshed and scoped per person

Vercel Connect

Build OAuth flows yourself

Build OAuth flows yourself

Build OAuth flows yourself

Rows marked “all have it” are table stakes. The rest is where the setup work hides.From public docs, Oct 2026 ·

Cohostly is shaped for many small tools. Big, high-traffic or multi-service systems may fit the others better. Read the long version

VIII. Made for the software you actually need

Not every useful app needs a million users.

resume-editor · liveHelped with the migration…Led the migration of 4 systems.Sofia’s friendsno key

i.AI resume editor

Friends open a link and get suggestions. No keys to paste.ai · context · link

team only

ii.Small-team dashboard

Only your team can open it, and the numbers live in its own database.team visibility · data

MTWTFweekly-reportMon 8:00Priya approvedsent

iii.Automated reporting

Runs on a clock, reads a sheet, and waits for a yes before sending.cron · connections · approvals

Renew passportBook dentistjust Leoprivate

iv.Personal workflow app

Private to you, its data kept and backed up. It rests when you do.private · data · backups

IX. For people who can’t stop building

A home for all the little things you make.

One useful tool becomes five. Five become twenty. A script that saves an hour. An internal dashboard. A weekend experiment. They all deserve a place to run—without becoming twenty separate infrastructure projects.

budget-trackerinvoice-chaserstandup-notesresume-editorweekly-reportpto-calendarlead-scorerreceipt-sorter

Keep making software. Spend less time maintaining its setup.

X. Questions

Asked, and answered plainly.

POST CARD

QUESTION i.

Do I need a Git repository?

No. Run platform deploy in the folder, upload the folder or a .zip in the dashboard, or ask your assistant to deploy over MCP. If you already use GitHub, you can connect a repository instead.

— the Cohostly team
i.COHOSTLY
TO
You,
builder of small things
somewhere with a good idea

Small software. Less infrastructure drama.

You’ve already built it. Put it to work.

Bring your working code to Cohostly. Get it online, give it the capabilities it needs, and let people actually use it.

Contact

Leave a note by the gate.

Dear Cohostly,
my name is and I’d like to talk about

Write back to me at .

COHOSTLY
Or write directlyhello@cohostly.cloud
Find us