A few things you
might be wondering.

d2o is currently invite-only. Public signups are coming soon. If you’d like to discuss access, tell us about your project. Already invited? Follow your invitation or sign in.

Current users admitted on a complimentary basis have free access during the invite-only period, within their resource allowances. New customers may be offered paid services. Any charges must be disclosed and agreed before paid services begin; complimentary accounts do not automatically become paid accounts.

See Pricing & access for how to get started.

Your organization has resource allowances for compute, database storage, object storage, and outbound bandwidth. Capacity is organized by environment type, and the dashboard shows your limits and usage.

Changes that would exceed capacity are blocked. Existing resources keep running. Contact us to discuss additional capacity.

d2o supports builds for Node.js, Ruby / Rails, Python, and Rust. Run web applications, APIs, and background workers alongside managed databases and object storage. See the platform overview for the supported services.

No. d2o uses buildpacks to turn your source into a runnable image using the runtime you select. You configure your application’s start command and environment, then push your code.

Push your code to the build branch of the Git repository hosted by d2o. The platform builds your application, and Automatic deployment rolls out successful builds automatically when enabled. You can turn it off to deploy a completed build yourself.

Direct builds from external Git repositories are not currently supported. The dashboard and CLI provide the commands to push to d2o. Walk through the workflow.

Yes. Web apps receive a platform HTTPS address, and you can add custom domains. After you configure DNS and verify ownership, d2o manages the TLS certificate for your domain.

Promotion deploys an already-built application image into the next stage without rebuilding it. Data, secrets, and environment variables remain separate in each environment.

Stages configured for promotion can also roll back to a previously deployed image. Database migrations and other data changes need their own recovery plan.

PostgreSQL, MariaDB, Redis, and MongoDB are available as managed services. d2o provisions the database and provides connection credentials for your application. See database capabilities for each engine.

PostgreSQL and MariaDB have automatic backups, with restores coordinated through support. Redis and MongoDB do not currently include automatic backups. Keep independent copies of important data. Deleting resources may also permanently delete their backups; no post-deletion recovery window is promised. See Database Backups for the current capabilities.

For a qualifying d2o outage, we automatically adjust the affected paid service charges for the time the service was unavailable. Unpaid charges are reduced; for amounts already paid, you receive a credit and can request a refund instead. Monthly minimums do not cancel the adjustment. Complimentary services receive no monetary adjustment.

This is a prorated charge adjustment, with no minimum uptime percentage promised unless agreed in writing. The Outage Adjustments Policy explains what qualifies, how we calculate it, and how to report a missed outage. The Terms address lost revenue and other business losses.

Availability depends on the service. Apps can run multiple replicas, PostgreSQL offers an optional synchronous standby on another node, and the HA object storage tier replicates data across storage nodes. MariaDB, Redis, and MongoDB currently run as single instances.

Singleton apps run one instance and briefly stop during deployments. See availability and recovery to choose the setup your workload needs.

Both tiers provide S3-compatible buckets. Capacity storage is intended for large amounts of data without high-availability. HA storage replicates data across storage nodes for resilience against node failure.

The d2o documentation covers setup, apps, deployments, data services, team access, and the CLI. For a quick introduction, start with How it works.

Email support@d2o.io with your organization, project, and a short description of the issue. Include relevant error messages, but leave out passwords and tokens. Our Contact page also covers general inquiries and legal or privacy requests.

Support follows your service arrangement. Continuous staffing and response or resolution deadlines are not promised unless expressly agreed in writing. This does not change our obligation to provide qualifying outage adjustments.