One console for every project and environment

Create projects, map up to 8 environments to git branches, invite your team, and keep keys and secrets.

Start freeRead the docs

What you manage in Blocks OS

Environments mapped to branches

A project holds up to 8 environments, from Development on dev to Production on main. Each one has its own data, its own X-Blocks-Key and a default domain, and takes a custom domain with two CNAME records.

Your team and their access

Invite people by email. The project owner creates environments, decides who can reach each one, and can hand ownership to someone else.

Secrets with an audit trail

Store API keys as named secrets. Rotate, lock and restore them, choose who can read each one, and check the audit trail.

Sign-in and provider settings in one place

OIDC clients, client credentials, external identity providers, MFA, CAPTCHA, and the email, notification and storage providers for each environment all live in the Secrets & Configs workspace.

Copy data between environments

Move chosen services' data from one environment to another, with an optional overwrite. Each migration is confirmed with a one-time code.

Connected GitHub repositories

Connect GitHub through SSO and pick the repositories your environments deploy from.

Set up a project from the console or the CLI

The CLI covers sign-in, project selection, secrets and scaffolding. Adding environments and linking repositories happens in the console.

  1. Create the project

    Sign up at os.seliseblocks.com with email, GitHub, Google, Microsoft, LinkedIn or X, then create a project. An account can own up to 10 projects.

  2. Add environments

    Add the environments you need and map each one to a branch, such as stg for Staging and main for Production.

  3. Connect your app

    Put the environment's X-Blocks-Key in your app's config, or run blocks new web to scaffold a React app that is already wired to it.

# Sign in and pick the project
blocks login --account <name>
blocks projects list --json
blocks use <tenantId> --account <name>

# Store a secret; the CLI never prints its value
blocks secrets set stripe-api-key --value-file ./key.txt --description "Stripe live key" --dry-run --json

Environments and their branches

  • Developmentdev
  • Testingtest
  • Stagingstg
  • IATiat
  • UATuat
  • Prod Shadowprod-shadow
  • Pre-Prodpre-prod
  • Productionmain

Recent changes to OS

All OS updates

Questions about OS

What is the X-Blocks-Key?

The public key that identifies one environment of your project. Your app sends it with every request to Blocks. It isn't a secret, so it can sit in your env files.

How many environments can a project have?

Up to 8: Development, Testing, Staging, IAT, UAT, Prod Shadow, Pre-Prod and Production, each mapped to a git branch. Each environment has its own data, and you can copy data between them.

Can I manage everything from the CLI?

Sign-in, project selection, secrets, OIDC clients and scaffolding work from the CLI. A project created from the CLI starts with one development environment. Adding more environments and linking repositories happen in the console.

How many projects can I create?

An account can own up to 10 projects.

Start with a free project

Sign up at os.seliseblocks.com and create a project, or paste one prompt into Claude Code, Codex or Cursor and let your agent set it up through the Blocks CLI.

Start freeSpeak to a Consultant