Questions, answered plainly.

A place to put the small apps your AI assistant builds and share them with other people. You deploy from your project folder, and Cohostly provides the hosting, sign-in, a database, AI model access, connections to Google and Microsoft, scheduled jobs and approvals, so you do not wire those together yourself.

Anyone who builds tools with Claude Code, Cursor, Codex or a similar assistant and wants teammates, clients or friends to use them. You do not need to be a full-time developer. The aim is that sharing a small app feels like sharing a document.

No. You deploy straight from a folder on your computer. You can also deploy a .zip or a GitHub repo, but nothing requires Git.

Anything that can run a command or speak MCP. You can deploy with the cohostly command, or connect your assistant to the Cohostly MCP server and ask it to deploy for you.

Small, purpose-made tools: a team dashboard, a signup sheet, a client portal, a morning summary, an internal form. Apps used by a handful of people and quiet most of the day suit it best.

Large, busy products and always-on systems. Apps sleep when nobody is using them, and a single run has a length limit. A big, high-traffic or multi-service system may fit another host better.

Install the command line with npm, sign in with cohostly login, start a tiny app with cohostly new, then run cohostly deploy. You get back an address. The quickstart takes about five minutes.

Node, Python and Go apps, and folders of plain web files. The starter templates cover static sites, Flask, FastAPI, Express, Go and Next.js. Supported versions are Node 16, 18 and 20 to 24, Python 3.9 to 3.13 and Go 1.18 to 1.29.

Not by hand. Cohostly drafts the settings from your code and asks you to confirm them. They live in a file called cohostly.json, which you can edit when you want more control.

Node.js 20 or later, on macOS or Linux. Windows works through WSL2 for the snapshot and check commands. Docker is needed only for cohostly check, which builds your app locally to prove it works.

Yes. cohostly check builds the app on your machine the way the platform would, and the develop commands let you run it locally with the platform’s services.

Up to 10 minutes, with about 1 MB of build log. Folders such as node_modules, .git and .next are left out of the upload already, so leave out build output and large data files too.

The error names the reason, and a failed deploy comes with a ready prompt you can paste to your assistant with the whole log. The common causes are a missing secret, an app that listens on the wrong address or port, and a limit being reached.

Usually it listens on 127.0.0.1 instead of 0.0.0.0, ignores the PORT variable, or writes files to disk that do not last. The how-apps-run page lists the five facts that explain most surprises.

Choose who can open it with the share command or in the dashboard, then send the link. A new app starts with a guest list of one: you.

Five: private (only people you invite), account (everyone in your team’s account), signed_in (anyone with a Cohostly account), link (anyone with the link) and public. Pick the narrowest one that does the job.

A new app starts with only you on the list. You widen it when you are ready.

Use cohostly share invite with their email. Someone who already has an account gets access at once. Anyone else gets an invitation that lasts 14 days, and has no access until they confirm.

A viewer can open the app and see its versions. An editor can also deploy, promote, roll back, change settings and see logs. An admin can also change sharing. On an account there are owners, admins and members.

Within about 30 seconds. Access is checked on every request, at the edge, before a visitor reaches your app.

A browser that is not signed in is sent to sign in. A script, or a signed-in stranger with no access, sees a plain "not found".

Yes. Add a custom domain to an app with the domains command. A custom domain is also the right choice if you set up your own login provider, because the default address can change if the link is reset.

Yes, but choose carefully: Cohostly’s checks come first. For an app with its own sign-in, set visibility to public or link, otherwise visitors are stopped before they ever see your login page.

A checkpoint where a person says yes before something important happens. When an assistant deploys, the new version can wait for approval. Your own app can also ask a person to approve an action, such as deleting rows or emailing a list, before it runs.

The people the account allows. Some requests, such as opening an app wider or raising a spending limit, are held until an account owner or admin answers, and deciding one requires being signed in to the dashboard.

It expires, and an expired request counts as a no. Your app should treat every answer except "approved" as "do not do it".

In Cohostly’s secret store, never in your code, a chat or a settings file. You list the secret names in cohostly.json, set the values with cohostly secrets, and your app reads them from its environment.

The value goes from your keyboard into the secret store and does not pass through the assistant. An assistant cannot add an AI provider key for the same reason: it would pass through the assistant.

Yes. A connection can be set so every call that changes something, such as sending an email or editing a sheet, waits for a person to say yes.

Yes. Every deploy is a numbered version. Promote an older one or roll back, and nothing is rebuilt, so it is quick. The newest 10 versions can be promoted.

Yes. The account keeps an activity log of changes, including ones made by an AI agent.

A service Cohostly lends your app. You declare it in cohostly.json, and the platform gives your app an address and a token for it. The real keys behind the service never enter your app.

Yes. The AI binding lets your app ask a language model a question without holding a provider key. A gateway checks the model, the rate and the budget on every call.

The platform pays for a small set of models. For others, such as the Claude models, you bring your own key from the company that makes them, and that company bills you directly.

Yes. Managed data is a small hosted SQLite database for each project. Your app never holds a connection string. Rules written above each table decide who can read and who can write.

It is a small database, not a data warehouse: no joins through the data service, no multi-statement transactions, and one writer at a time. A read returns at most 1000 rows.

Yes. A connection lets your app use someone’s Google or Microsoft account after they agree once on a consent screen. Your app never sees a password or a token. Slack is not available yet.

Your choice. In owner mode everyone acts through one connected account, such as the shop’s own sheet. In visitor mode each person connects their own account, and the app acts as that person.

Yes. The clock binding runs your code at times you choose, such as every weekday at 9:00, in the time zone you set. It records every run, retries failures and stops two runs overlapping.

A sleeping app runs no code, so a timer inside it stops. The platform keeps the clock outside your app and wakes the app when a job is due.

After 10 minutes with no visits by default, it goes to sleep, and the next visit wakes it. The first visit after a sleep is slower, so open it yourself before showing it to someone.

Not reliably. Files can disappear on a restart, a new version or a long sleep. Keep anything that matters in the managed database, which survives restarts and returns with the right version on a rollback.

If the project is marked stateful, the command line can back up and restore its /data folder, up to 256 MiB. A backup is a safety copy, not a promise that the disk lasts.

512 MB by default, and you can choose 256, 512, 1024 or 2048 MB. The account has a limit on the total memory of apps awake at the same moment. A sleeping app does not count.

0.0.0.0, on the port in the PORT variable. After a deploy the platform asks your health address until it answers, for up to 5 seconds by default.

Yes, in the dashboard and from the command line, along with the version history to compare against.

At the moment: 5 projects, 2 apps running at once, 2048 MB of memory across running apps, 10 deploys an hour and 40 builds a day. The docs call these starting values that may change.

The message names the limit, says what your account has and how to raise it. A refused action is a 403, and at the web address itself it is a 429.

By default $2.00 per project per month and $10.00 per account. A call that would pass a cap is refused before anything is spent.

Rate limits apply at the edge: 600 requests a minute from one network address to one project, and 6000 from everyone. Only the address over its limit is refused.

Yes. The cost command and the dashboard show usage per app. Pricing is not set, so costs shown are estimates, and compute time and AI spend are not measured everywhere yet.

Pricing is not published yet, and costs shown today are estimates. Email us and we will tell you where things stand.

cohostly login shows a code, you approve it in the dashboard, and a key is handed over once. It is saved in a file only you can read. Scripts and CI use an API key that starts with plk_.

You sign in once in the browser and approve a consent screen. Access lasts 30 minutes and refreshes for up to 30 days.

Shared secrets, AI provider keys, connections, API keys, the activity log, approval rights and usage.

Apps, secrets and connected accounts belong to you. The privacy page describes exactly what the website and dashboard measure and what they never collect.

At cohostly.cloud/docs, with a quickstart, every command, the SDK, each binding and sample apps.

Email hello@cohostly.cloud, or use the contact form on the home page.