Skip to content
CloudHike.dev
Get $10 free
ENVIRONMENTS

Test in development.
Ship to production.

Every project starts with production. Add a development environment next to it, with its own database, bucket, Redis, keys and .env. Nothing is shared, so work in development never touches real data.

Start free with $10 Read the docs
Separate services One switcher API, .env and MCP aware
ENVIRONMENTS · LIVE
DEVELOPMENTmy-app-dev.envPOSTGRESAUTHSTORAGEREDISPRODUCTIONmy-app.envPOSTGRESAUTHSTORAGEREDISISOLATEDNOTHING CROSSESDEVPROD
2environments per project: production and development
0databases, buckets or keys shared between them
1 .envper environment, from the dashboard, API or MCP
WHAT YOU GET

Everything included.
Nothing to wire up.

Production and development, each with its own services, keys and .env.

Separate services

Development starts empty. Deploy the Postgres, Auth, Storage and Redis it needs, and they never share anything with production's.

Own keys and variables

Each environment has its own credentials, custom variables and .env file. A leaked development key opens nothing in production.

One switcher

Switch from the project header and stay on the same tab. Development lives at <slug>-dev and its pages carry a tag, so you always know where you are.

API and MCP aware

Production is the default. Add ?environment=development to the API and .env download, or pass the environment argument to the MCP tools.

Localhost uploads in development

Development buckets already accept browser uploads from http://localhost on any port. Production accepts only the sites you list.

Safe to throw away

Delete the development environment from Settings and only its services go. Production is deleted only with the whole project.

HOW IT WORKS

Three steps
to production.

  1. 01
    Add development

    Open the switcher under the project's name and add a development environment. It starts empty.

  2. 02
    Deploy its services

    Deploy the services development needs. Each gets its own credentials and its own .env.

  3. 03
    Build, then ship

    Point your local app at development's .env and your live app at production's. Switch any time.

Read the Environments guide
Terminal
# Production's variables (the default)
curl -fsS -H "Authorization: Bearer <access token>" \
  "https://cloudhike.dev/api/projects/<project id>/env" > .env.production

# Development's variables, for your machine
curl -fsS -H "Authorization: Bearer <access token>" \
  "https://cloudhike.dev/api/projects/<project id>/env?environment=development" > .env.local
BETTER TOGETHER

One project.
Every service connected.

Same project, same .env, same bill.

Postgres

Managed Postgres 16 with pooling, backups and a SQL editor.

Explore Storage

A private S3-compatible bucket per project, with a file browser and presigned URLs.

Explore MCP server

Connect Claude Code, Codex, Cursor, VS Code and other AI editors to your backend with MCP.

Explore
FAQ

Questions about
Environments.

Does development share data with production?
No. Each environment has its own services, keys, custom variables and .env. Nothing crosses between them.
How do I reach development from the API or MCP?
Production is used by default. Add ?environment=development to API calls and the .env download, or pass the environment argument to the MCP tools.
Does development cost extra?
Its services are billed like any others. On Pro, new databases in development start at the smaller Dev size instead of Standard.
What happens if I delete it?
Deleting the development environment removes its services only. Production stays until you delete the whole project.

Add Environments to your project.
Free to start.

Postgres, auth, storage, Redis, email and AI models. One API key.

Start building for free See pricing