Cohostly
How it works

From a folder to a link your team trusts.

Six things happen between “my agent built this” and “we use it every day”. You make the choices. We do the rest.

I.

Drop in your project

A folder, a .zip or a GitHub repo. Your assistant can send it too. We work out what it is and how to run it, and show you the settings before anything goes live.

See it from your assistant
Putting budget-tracker online
Uploaded42 files
Recognised a Flask appPython 3.12
Suggested 512 MB, rests when idleDraft
II.

Get one link

Your app gets an address like a shared doc. It stays the same through every update, so the link you sent last month still works.

Read: your agent built a tool
budget-tracker.cohostly.cloud
LiveVersion 5
Opened by4 people this week
Last updateToday, 10:42
III.

Choose who can open it

Share by email, like a document. Keep it to named people, your whole team, anyone with the link, or the public. Change it any time.

Open the dashboard
Who can open it
Maya RaoOwner
Arjun MehtaCan edit
Leo ParkCan use
Anyone at NorthwindCan use
IV.

Connect accounts, one permission at a time

Your app can use Gmail, Sheets, Drive or Slack without ever seeing your password. You pick exactly how much: read only, or read and write.

How keys stay hidden
Accounts this app can use
GmailCan send emails
Google SheetsCan read and edit
Google DriveCan open files
SlackCan’t use
V.

Updates wait for your OK

When someone you’ve shared with changes the app, nothing changes for your users until you approve it. Each update is explained in plain words, with how risky it is.

Why apps should ask first
Waiting for you
Arjun: “Add a Travel column”Safe to approve
Priya: “Email a weekly summary”Worth a look
VI.

It rests when no one’s using it

Apps sleep when idle and wake in about a second when someone opens the link. You pay for the time it’s used, not for the hours it waits.

Why our apps nap
This week
Awake6 h 40 min
Woke up52 times
Resting161 h
Put your first app online.