runlot docs

runlot deploys your worker together with PostgreSQL, login, file storage, email, Git hosting, and domains. Find everything about setup, deploys, data, code, and domains here.

Two commands take you from an empty folder to a public deploy URL.

npm create runlot@latest
runlot deploy

Where to start

Setup and first deploy

Get a live deploy URL in five minutes.

Project structure

Learn about runlot.json, the worker entry point, and the static assets directory.

Your first query with env.db

Use your database without a connection string.

Connecting with psql

Connect with the PostgreSQL tools you already know.

Everything a project can declare

One line each in runlot.json, and the deploy creates what is missing.

App login

Email and social login, sessions, and env.auth in your worker.

File storage

env.storage for uploads, plus signed URLs with an expiry.

Email

Send from env.email and receive mail at your project address.

Scheduled execution

A cron schedule that runs your worker's scheduled handler.

Repositories

Git hosting on our domain over HTTPS and SSH, browsable in the dashboard.

Domains

Connect a domain you own, run DNS zones on our nameservers, or search for a new one.

How these docs are written

Anything we don't offer yet is marked as such. Pages for features still in progress carry a Coming soon badge at the top, and pages that run against a test environment carry Test mode.
The CLI and API references are generated from code. The CLI and API references are generated to reflect changes to commands and APIs.
Only limits we actually enforce are documented. The limits table lists the limits the service enforces today.

If you need help

If you couldn't find an answer in the docs, tell us at hello@runlot.io. We'll add what you needed.