BETA TERMS

Beta terms and limits

dFlow is in beta. The product can change, and we offer no SLA or uptime promise. Read these terms before you deploy apps that matter.

01

What beta means

This service is a beta. There is no uptime promise. Data can be reset, and a reset can remove accounts, applications, and databases. Stay inside the caps below. The operator can suspend a workspace for abuse.

Signup stores a terms acceptance only when the API setting DFLOW_TERMS_VERSION is set. That setting stays empty until the text at docs.k8s.dflow.sh/docs/terms is signed off. The version on that page is beta-2026-11.

02

Limits and caps

These are the default limits on each workspace. An operator can raise one workspace. The defaults are not a price.

ResourceBeta limit
Environments2
Apps5
Databases2
CPU2000m
Memory4Gi
Storage20Gi
Replicas per app3
03

Your data and backups

You can create a PostgreSQL backup on demand, list backups, and restore one. A restore sends the header Confirm-Name, and it must equal the source service name. The CLI flag is --confirm-name. When the object store driver is s3, a new PostgreSQL database also gets a daily backup at 02:00 UTC, kept for 7 days, and WAL archiving to that store. An empty driver, or the filesystem driver, leaves a new database on the machine. Deleting the database does not delete a bucket copy. Valkey has no backup command. This is not an uptime promise. Keep your own copy of data that matters.

04

Support

Write to hello@dflow.sh. This beta has not named a separate support channel.

05

How we announce changes

We post each change in the public changelog. Each entry has its own link.

Get a beta invite.

The beta is invite only. Tell us what you deploy and which agent you use. We reply by email.

Join the beta

Open to the first 100 users.

Book a design-partner call

Invite only. Read the beta terms.