[ beta limits ]
Dexaflow Cloud closed beta: limits
The Free plan of Dexaflow Cloud is, for now, a closed beta: free, by invitation from the waitlist, for organizations only, with a corporate email and no SLA. It runs on shared capacity, so every organization gets the limits below. They may change during the beta; when they do, we update this page. The Beta Terms of Use apply, and this page is part of them.
Limits per organization
| Limit | Beta value |
|---|---|
| Users per organization | 3 |
| Organizations per person | 1 |
| Active DAGs | 10 |
| Minimum schedule interval | 15 min |
| DAG runs per day | 50 |
| Concurrent tasks | 2 |
| Maximum task duration (a task still running a few minutes after this is stopped) | 30 min |
| Resources per task (default / maximum) | 0.5 vCPU, 1 GiB / 1 vCPU, 2 GiB |
| Task network access | Outbound only, to public internet addresses on ports 80 and 443 (HTTP and HTTPS) |
| Where your data is stored | United States (Google Cloud, region us-east1) |
| Retention of task logs and run history | None guaranteed: may be deleted at any time |
| Inactive accounts | May be suspended or deleted, with notice by email first |
| End of the beta | All data deleted within 30 days, unless you move to a paid plan |
Some of these limits are applied automatically and others by monitoring and by hand. Please stay within them anyway: going over a limit, or working around one, may get tasks stopped, DAGs paused or access suspended.
Known limitations
- No SLA. Support is best effort, on business days, at [email protected].
- Preemptible capacity. Tasks run on spot machines that can be reclaimed; an interrupted task is retried and counted as an infrastructure failure, not yours.
- Cold starts. The first task after a quiet period can take a few minutes to start while capacity scales up.
- Sandboxed tasks. Each task runs in a sandbox, which makes heavy disk I/O and system calls slower.
- Curated images only. Tasks run on DexaData base images (Python and dbt); your own container images are not supported in the beta.
- Network. Tasks can open outbound connections only to public internet addresses on ports 80 and 443 (HTTP and HTTPS). Other ports, including database ports such as 5432 or 3306, and private networks are blocked, so tasks cannot connect directly to a database; use an HTTPS API instead.
- Airflow compatibility. Some Apache Airflow features are not supported yet; see the documentation.
- AI features. Features marked "coming soon" on this site are not part of the beta.
- No retention promise for logs and history. Task logs and run history may be deleted at any time during the beta; do not rely on them as storage.
- Your data may be deleted. Keep DAG code in your own repository and do not use production data, production credentials or sensitive personal data.