Data

Environment & secrets

Share env at the project level and override per service. Static sites bake public vars at build time; web workers get runtime injection.

Screenshot coming soon

Saving env that requires a new process or build queues a redeploy. Public prefixes like NEXT_PUBLIC_* are treated as non-secret by design.

Platform-injected metadata (PORT, DATABASE_URL, BYTSTACK_*) sits alongside your own keys without colliding when you follow conventions.

Two scopes

Project shared env plus service overrides.

Build vs runtime

Static rebuilds on change; containers pick up runtime env.

CLI set

bytstack env set KEY=value for quick updates.

Explore more

Provision, connect, back up, and rotate credentials.

Isolated data for pull request apps.

Connect GitHub — every push builds and ships.

Connect a repo. Deploy Node with Postgres, domains, and previews in one place. No lock-in tax — just the path from push to production.