Hosting, PostgreSQL, login, file storage, email, and Git repositories in a single project. Ship a Next.js app or a small API without configuring a server.
runlot deploy
Bundling…
Bundled 12 files, 84.2 KiB
Uploading… (84.2 KiB)
Deploying…
v3 9f2c… 2026-09-16T04:12Z
→ https://my-app.me.runlot.dev
Next.js
Hono
Prisma
Drizzle
TypeORM
Knex
Sequelize
SvelteKit
Astro
Nuxt
React RouterCreate it, deploy it, add what you need. After installing the CLI and logging in, these three commands are all it takes.
$ npm create runlot my-appPick Next.js, Hono, or a static site. The runlot.json and the rest of the setup are already in the template.
When the deploy finishes you get a URL that already works.
$ runlot deploymy-app is the project and me is your personal organization.
One line each in runlot.json, and the deploy creates them. Your app code reaches them through env.
{
"database": true,
"auth": true,
"storage": true,
"email": true
}There is no command to turn them on. Declare only the ones you need.
Create a project and the rest comes with it. There is nothing to sign up for separately and nothing to wire together.
The SQL and transactions you already know. Reach the same database from your app through env.db, and from your terminal through psql, pgAdmin, or the ORM you already use.
$ psql
runlot=# select * from users limit 4;
| id | name | active |
|---|---|---|
| 1 | jiwoo | true |
| 2 | minseo | true |
| 3 | haneul | true |
| 4 | seojun | false |
users · 4 rows
Email and social login with GitHub and Google, plus session handling. Identify the user in your server code with env.auth.user() and control which data they can reach.
Upload images and attachments through env.storage, and share them through signed URLs that expire. Credentials are never exposed to your worker code.
Every project gets a mail address. Send with env.email.send, and mail sent to that address reaches your worker's email() handler. What went in and out is in the dashboard.
Create a repository inside the project and push over HTTPS or SSH, and the commits and files are right there in the dashboard.
Add a CNAME and a TXT record to a domain you already own and it is connected. Certificates are issued and renewed for you.
Every commit is shipped, encrypted, about once a minute. Pick any backup, commit, or moment in the dashboard and restore to it.
With no requests coming in, your app stops running and starts again on the next one. Your data and settings stay exactly as they were.
import { Hono } from "hono";import { Pool } from "@runlot/pg"; const app = new Hono<{ Bindings: Env }>(); app.get("/posts", async (c) => { const user = await c.env.auth.user(c.req.raw); const db = new Pool({ db: c.env.db }); const { rows } = await db.query( "select id, title from posts where owner = $1 limit 20", [user.id], ); return c.json(rows);}); app.post("/upload", async (c) => { const form = await c.req.formData(); const file = form.get("file") as File; const url = await c.env.storage.put("covers/" + file.name, file); return c.json({ url });}); export default app;env.No connection strings or API keys to configure. Reach them through env, with the frameworks and ORMs you already use.
$1env APIThe things you used to configure and operate service by service live inside one project.
Compiled from each service's public documentation and pricing pages as of September 2026. We do not re-check them on a schedule, so tell us if something has changed.
AI coding tools made building an internal tool easy. Deploying it still means asking someone. On runlot, who built it and what data it touches is attached from the start — so there is nothing left to explain to your security team.
Create an organization and invite people. Admin, member, and viewer roles decide who deploys and who only looks.
Set project access to organization members only and nobody else reaches it. The check runs before your app code does, so you do not rebuild a login screen per app.
Dozens of internal tools, each with its own PostgreSQL. The project list tells you which data sits where.
If your data cannot leave the company, an install on your own infrastructure is on the roadmap — talk to us about the timing.
Talk to us about teamsNothing is charged within the free plan — not even with a card on file.
Enough for personal work and side projects.
$0/ mo
For running what you built on your own domain.
$20/ mo
For companies where several people ship internal tools.
Talk to us
On the free plan it never turns into a bill. Requests stop for the rest of that day, and start being served again the next day. On Pro, only usage above what is included is billed, and a monthly spending limit is on by default so it cannot climb past it. We tell you before you get close.
Yes. Run runlot deploy from your existing repository. It recognizes the framework and writes the configuration it needs. For the database, a pg_dump file loads straight in.
Yes. It is standard PostgreSQL, so pg_dump works as it always does. Files are plain objects, and env.storage.presign hands out a signed URL for any of them. Nothing is kept in a format that locks you in.
Seoul, for now — one region. Your app and your database sit in the same place, so a database call never crosses a network. Users far from Seoul will see slower responses. We will announce other regions as they open.