FAQ

Find answers to common questions about supported apps, pricing, access, and data. Follow the links in each answer for detailed instructions.

Supported apps and runtime

Can I deploy an app built with Lovable, Bolt, or v0?

It depends on how the app is built. Start by asking the AI tool that created it, or an AI agent that can inspect its code. You can copy this prompt:

https://keelson.dev/llms.txt

Read the documentation at this URL and follow relevant links as needed.
Check whether this app can be deployed to Keelson.
Review its code, configuration, database, authentication, and external services,
then explain the changes and preparation needed.
Ask me if you need more information to make that assessment.

Prebuilt HTML, CSS, and JavaScript can be deployed as a static site. Apps with server-side processing, such as Next.js apps, can be deployed as web apps. Build static sites locally and configure their external service URLs before deploying.

You can keep databases and storage that accept external connections, but data and authentication tied to the app-building tool do not move automatically. See Bring an existing app.

Can I run my app outside Keelson?

Yes. With the configuration and code changes needed for the destination, your app can run locally, on another hosting service, or on your own server.

Provide the runtime, such as Python or Node.js, install dependencies, and configure startup and database connections for the new environment.

If you still need the login, access controls, and scheduled jobs that Keelson handled, you must provide them in the new environment. Adapt code that reads Keelson’s signed-in user information to your new authentication method. Code using the Files / Media SDK also needs changes for the destination’s storage service, along with migration of the files.

Does Streamlit work?

Not currently. Streamlit requires WebSockets, which do not fit Keelson’s execution model. Gradio is under evaluation. See Supported apps and constraints.

Can I use Django?

Yes, as long as it connects to an external database such as PostgreSQL. Managed SQLite (libSQL) has no backend for the Django ORM, so Django with Managed SQLite is not supported. Set db.mode: none, pass the connection details as secrets, and start it with gunicorn. See Framework notes.

Is my app always running?

No. Web apps stop after a period without requests and start again on the next request. The first response after stopping may therefore take longer.

Use scheduled jobs for work that must run at a set time. Work that continues after a response has been sent is not guaranteed to finish. See When apps run.

Pricing and limits

When does billing start?

For first-time users, billing starts when the 14-day free trial ends and the workspace moves to a paid subscription.

• Starter / Plus: you can try these without a payment card. If you do not add a card before the trial ends, you are not charged. If a card is on file, your paid subscription starts and the first charge occurs when the trial ends.
• Team: a payment card is required to start the trial. Cancel during the trial to avoid a charge. If you continue, the first charge occurs when the trial ends.

If the trial ends without a paid subscription, new deployments, app startup, and scheduled jobs stop being available. See What happens after a trial or subscription ends? below for how data is handled.

If your account has already used its trial and you create another workspace, billing starts when payment completes. See Billing and subscriptions.

Which plan fits two developers and 50 app users?

Plus or higher. Developer seats are for members who build and manage apps. Two people doing that work need two seats. The 50 people using the apps can join as App Users, and their number does not affect the price.

Owner, Admin, and Developer roles count toward developer seats. Also check that the concurrent app limit fits your needs: Starter allows 1, Plus 2, and Team 4. See Plans and limits.

If I keep 10 apps but only use a few at a time, which limit matters?

Paid subscriptions have no limit on the number of apps stored in a workspace. The app-count limit applies to apps used concurrently.

Apps accessed within the last five minutes occupy a concurrent app slot. When requests stop, an app becomes sleeping and its slot is released.

During the trial, a workspace can also hold at most three apps. Apps already deployed as static sites do not count toward those three. See Concurrent apps.

What do users see when all concurrent app slots are occupied?

Someone opening a sleeping app sees a page asking them to wait for a slot. An unreserved slot becomes available about five minutes after the last request to the app using it. It stays occupied while that app continues to receive requests. Priority startup can reserve a slot for an important app (Plus and higher on paid subscriptions; all plans during the trial).

Are external API costs, such as OpenAI usage, included?

No. External API usage is billed separately under your agreement with that provider. Store the API key as a secret for your app to use. See External integrations.

Access and data

Can anyone with the URL open my app?

No. A visitor must be signed in as a workspace member and have permission to view that app. Visitors who are not signed in see the login page. To share with someone outside your company, invite them as a member; App Users are unlimited. See Authentication and login.

Where do apps and databases run? Are databases backed up?

Apps and their Managed SQLite databases are hosted in the region chosen when the app is created. The default is Japan.

Japan is currently the only region available. US West is in preparation; selecting it before release is rejected.

Managed SQLite includes backup and restore on every plan. Files stored through the Files / Media SDK and external databases are not included in these backups.

Daily backups, manual backups, point-in-time recovery (PITR), and downloads are available. See Backup and restore.

Will updating an app erase saved data?

A normal redeployment does not erase data in Managed SQLite or files stored through the Files SDK or Media SDK. Local files on the app server, however, are lost on restart or redeployment.

If a database migration or your app code changes or deletes data, those changes take effect. See Databases for storage options and Update and restore for recovery.

What happens after a trial or subscription ends?

If a trial ends without a paid subscription, or a canceled subscription reaches the end of its term, new deployments, app startup, and scheduled jobs become unavailable. Apps and data are not deleted immediately.

Owners and Admins receive deletion notices in the console and by email for affected apps. From the time the notice is recorded, the grace period is three days for a workspace that has never paid, or 30 days for a workspace with a payment history. Check the notice for the scheduled deletion date.

Starting or resuming a paid subscription within the grace period cancels the notice and keeps the apps and data. Without a subscription, affected apps are automatically deleted after the grace period. Database backups and Files files are then retained in isolation from normal use for seven days, but recovery is not guaranteed.

Managed SQLite backups can still be downloaded during the grace period. Export Files / Media files before the subscription ends. See Apps and data after cancellation.

What happens if I downgrade?

A downgrade during a paid subscription takes effect at the end of the current billing period. You keep the current plan until then. Plan changes during a trial take effect immediately.

Changing plans does not itself delete apps or data. Usage may be restricted if you exceed the new plan’s limits. For example, sleeping apps cannot start while all concurrent app slots are occupied, and you cannot add members who build or manage apps while over the developer seat limit.

See Change plans for other limits.