Rescriptum
Browse docs

Docs / Workspace

Cloud and infrastructure

Pre-flight checks, deploys, serverless databases, and the project .env editor.

The Cloud and Infra panel is where a project goes from working on your machine to running somewhere. It checks readiness, deploys, provisions a database, and manages the project's .env.

Pre-flight

Five checks run against the open project and show as a score.

CheckWhat it looks at
Build PipelineA build command was detected for the project
Cloud Provider TokenA token for your host or database provider is connected
Git Working TreeHow many uncommitted files there are
Secrets Vault HygieneWhether .env still holds placeholder values or real ones
Serverless DatabaseA DATABASE_URL is present

Failing checks tell you what to fix; they do not block you from deploying.

Deploy

Pick a host and a target:

  • Hosts: Vercel, Cloudflare, or Netlify
  • Targets: production or preview

The agent can also deploy through deploy_to_cloud, subject to approvals.

Databases

Provision a serverless Postgres database on Neon or Supabase. The region defaults to aws-us-east-2 for Neon and can be changed. On success the connection string is written to your project's .env and shown masked in the panel.

For Neon, Rescriptum tries your existing Vercel login first (through the Vercel Marketplace, which also wires the database to the Vercel project). If that is unavailable, or you request a specific region, it uses a NEON_API_KEY instead.

The .env editor

An inline editor for the project's .env file, with placeholder detection so you can see which values still need real secrets. Sync pushes the variables to your cloud provider's environment settings. The agent has the same through sync_cloud_env.

Careful

.env files hold real secrets. Make sure .env is in your .gitignore. Rescriptum flags placeholders but does not rewrite your ignore rules.

Connecting providers

Provider access comes from a token in the project's .env (for example NEON_API_KEY) or from connecting the matching preset in MCP Config: Vercel, Neon, or Supabase. The Cloud Provider Token check tells you which is active. See Skills and MCP servers.

Suggested flow

  1. Get the build and tests green with the agent in Code mode.
  2. Open Cloud and Infra and clear the pre-flight checks.
  3. Deploy to preview and check the URL.
  4. Promote to production.