Real backends, real databases, one command · live now

Your agent writes it.Videan runs it.

Push code through one API, or run videan deploy, and get a live URL, auth, and a database in 60 seconds. No AWS account, no YAML, no Dockerfile.

videan deploy
$ videan deploy✓ pushed 23 files · snapshot ready✓ detected node · image built in 41s✓ postgres provisioned · DATABASE_URL injected● live at https://notes.videan.xyz
One platform

Stop wiring a stack per project.

Hosting, database, version history, and client access usually mean four products and a day of glue. Here it's one deploy: through the API, the CLI, or whatever your agent speaks.

Deploys like Vercel

Build, preview, promote, rollback. Containers or scale-to-zero serverless, from one command.

Postgres like Supabase

A real database per app: provisioned by one flag, isolated, backed up, queryable from the dashboard.

History like GitHub

Every push is an immutable version: inspect it, diff it, restore it. No repo to set up.

Sharing like Google Docs

Viewer or editor, per person. Private to public, per app. No accounts to provision.

How it works

From folder to production in three moves.

The whole contract is “expose an HTTP port”. Everything else is the platform’s problem: building, routing, TLS, identity.

01

Push

Your agent sends files over the API, or you run videan deploy. Every push is an immutable snapshot: the deploy history is the version history, no git required.

02

Build

Node, Python, Next.js, Go or your own Dockerfile: detected, containerized and built automatically. Need a database? postgres: true. That’s the whole config.

03

Live

A URL on *.videan.xyz with TLS, login in front of it, and identity injected as headers. Your app never implements auth. The edge already did.

Platform

Everything an app needs. Nothing it has to ask for.

Managed Postgres

One flag provisions a database, isolates it per app, injects the URL as a secret and backs it up before every deploy.

Auth at the edge

Four access tiers per app: private, org, signed-in or public, enforced before a request ever reaches your code.

Rollback in one call

Production is a pointer to a snapshot. Rolling back re-launches a known-good image. The current version serves until the old one is up.

A preview per deploy

Every deployment gets its own URL, pointing at exactly that version’s instances. Verify the new one while the old one serves.

Cron & background jobs

Schedules and queues call your app’s own routes: same code, same secrets, same database, testable with curl.

Logs, metrics, storage

Searchable logs, per-app request metrics, presigned object storage, secrets, custom domains, webhooks and an audit log.

Versioning

Every app carries its full history. Built in.

GitHub-style versioning without GitHub: every push is a version you can inspect, diff, and return to. Anyone with edit access can change the code or restore any previous version. No separate repo, CI, and hosting pipeline to wire together for every project.

Sharing an app with your team should be as easy as sharing a doc.
Not a weekend of AWS.

Every app is gated at the edge (private, org-only, signed-in, or public) and shared per person as viewer or editor. Give a client view access and a contractor edit access on day one. No accounts to provision.
For agents

Built to be called, not clicked.

deploy.ts
import { CloudClient } from "@videan/sdk";

const cloud = new CloudClient({ apiKey });

const app = await cloud.apps.create({
  name: "notes",
  postgres: true,
});

await cloud.apps.deploy(app.id, files);
// → https://notes.videan.xyz
  • Typed SDK and a plain HTTP API. Everything the dashboard does, an agent can do: deploys, logs, rollbacks, secrets, SQL.
  • Scoped service tokens. Mint a key confined to one app, with an expiry, and hand it to the agent that owns that app.
  • Readable failures. Build logs, crash detection and deploy status an LLM can act on, not a dashboard screenshot.
  • Zero tokens billed to us. Bring your own agent. We run the software it writes; we never sit in the loop.

Ship the next thing.

The client portal, the internal API, the backend your team asked for. Live today.