One Server
English
Sign up

Log in

Log in to your One Server account.

Continue with GoogleContinue with GitHub

or with email

Forgot your password?

No account yet? Sign up

Sign up

One account for your database and deployments.

Add a card after signing up and your project runs right away. At the end of each month the base fee and usage past the allowances are charged. Full pricing

Continue with GoogleContinue with GitHub

or with email

Consent
See what you agree to
Purpose
Forming the service agreement
What is collected
None
How long it is kept
Until you close your account. Contract and payment records required by the Electronic Commerce Act are kept for 5 years
Your right to refuse
You may refuse to consent. However, if you refuse, you cannot sign up.
See what you agree to
Purpose
Signing up and managing your account, providing the service, billing, answering inquiries
What is collected
Email address, password (stored encrypted), organization name, access records and usage records
How long it is kept
Until you close your account. Records a law requires to be kept are kept for the period it sets
Your right to refuse
You may refuse to consent. However, if you refuse, you cannot sign up.
See what you agree to
Purpose
Sending news of new features, advance notice of price changes, and event news
What is collected
Email address
How long it is kept
Until you withdraw your consent
Your right to refuse
You may refuse to consent, and refusing places no restriction at all on signing up or using the service. You can withdraw your consent at any time after giving it.

Read them in full in the Terms and the Privacy Policy.

Already have an account? Log in

Docs

Preview protection

Who can open preview addresses, and how automation gets through.

Preview protection

Pushes to branches other than the production branch are deployed to preview addresses. This decides who can open them.

get_preview_protection   the current setting, scope, bypass keys and share links
set_preview_protection   off | members | password
set_protection_scope     what is protected (previews | generated | all), addresses let in, paths that pass
create_bypass_secret     create a bypass key (shown once)
revoke_bypass_secret     revoke a bypass key
create_share_link        a link that opens one deployment or one branch (1 to 30 days)
revoke_share_link        revoke a share link
  • members: only people in this organization who are signed in to the console. The default for new projects.
  • password: with a single password. For showing customers who have no account.
  • off: anyone who knows the address.

The production address and connected domains are always public. The dpl-… address each deployment gets is protected even for production builds.

Where you cannot sign in, such as E2E tests, send a bypass key made with create_bypass_secret in the x-blackwall-protection-bypass header. An assistant checking a preview it deployed uses the same key. With scope generated in set_protection_scope, production's own address is protected too; with all, connected domains as well.

Environments

Beside production and branch previews, a project can make environments such as staging, each with its own address, domains and environment variables.

list_environments        production and the project's own environments, the branch each follows, address, domains
create_environment       create one (name, branch, auto_assign)
update_environment       change the branch it follows and whether it takes builds by itself
remove_environment       remove one (its name in confirm)
set_domain_environment   point a verified domain at an environment

Give an environment its variables with its name as the target in set_env_vars. One with auto_assign false changes only through promote_deployment. Only owners and admins can change environments.

Branch previews

get_branch_previews   the current setting (branch_previews: true | false)
set_branch_previews   enabled: true | false

An organization-wide setting. false builds only what reaches the production branch (usually main); a branch push stays in the deployment history as skipped. Redeploys, uploads and deploy hooks still build. Only owners and admins can change it. Over REST: GET·PUT /v1/projects/<ref>/branch-previews {enabled}. In the CLI: oneend deployments branch-previews [on|off]. In the console: Organization → Deployment policies → Branch previews.