dply is in private beta. You can deploy real apps and attach real resources, but the product is still changing, and some parts are rougher than they will be at general availability. This page covers what beta participants get, what it costs, the known limits, and how to tell us what you find.
Joining the beta
Sign-up is open. You don't need an invitation: create an account, then choose a plan. Beta participants get the same plans and limits as everyone else, with no extra perks.
If you received an invitation email, its link opens the sign-up form with your address filled in. Invitations expire after 30 days, but you can always sign up without one.
What it costs
Beta organizations use the same plans as everyone else. There is no free beta tier.
- There is no trial. Starter is $0 a month plus usage; Pro and Team bill from the day you choose them. Checkout asks for a card on every plan.
- Starter has a $25 spending cap on usage by default, which you can raise. Past it, builds and traffic pause until the next billing period.
- Static sites can also use the free tier with no card.
| Plan | Price | Seats | Extra seat |
|---|---|---|---|
| Starter | $0/mo | 1 | — |
| Pro | $29/mo | 3 | — |
| Team | $49/mo | 10 | $5/mo each |
| Enterprise | Contact us | Custom | Custom |
There's no per-app or per-site fee on any plan. Usage bills on top of the plan fee at the rates on Plans & pricing. See Starter and spending caps and Usage & metering for the full limits and rates.
What you can use
Everything in these docs is available to beta participants on the plan they choose, including all four runtime modes, resources, previews, custom domains, the CLI and the HTTP API. Some features need a paid plan or Team specifically; each page says so near the top.
Known limits
These are current gaps you may run into.
- Supported stacks. Python, Go and WordPress apps can't be deployed. See Frameworks & runtimes.
- Hugo and Jekyll. They are detected, but the build image doesn't include Hugo or Ruby, so their builds fail as detected.
- Choosing a runtime mode. The create page uses the mode dply detects. There is no picker for Worker SSR on the create page. The templates gallery can start an app in Worker SSR mode.
- Build settings at creation. The create page doesn't show the detected build command or output directory. Review them in Build after the app exists, and redeploy if you change them.
- Hybrid apps need a server you already run. dply serves the static files and proxies the rest to it.
- Container rollbacks rebuild the earlier commit rather than switching back instantly.
What may change
- Features and interface. Pages, labels and defaults may change between releases. These docs are updated as they do.
- Limits and prices. Plan allowances and prices may change before general availability.
- The end of the beta. No end date is set. When the beta ends, beta organizations continue on their current plan.
There are no beta-only terms and no service level agreement during the beta.
Feedback and support
We read every report. The most useful ones include the app name, the deployment ID from Deploys, what you expected, and what happened instead. For a failed build, include the relevant lines from Build & deploy logs.
Email hello@dply.io from the address on your dply account. We answer as quickly as we can on business days; there is no guaranteed response time. To report a vulnerability, email security@dply.io instead.
See Support and Report abuse.
Your data during the beta
If your subscription ends or a payment fails, your organization is paused: apps stop serving, containers and databases sleep, and builds stop. The organization resumes when you choose a plan. Your data is kept for 30 days after the pause; we email you before it's deleted, and after 30 days the organization's apps, resources and data are deleted permanently. See Paused accounts.
Warning
Keep your own backups of anything you can't recreate. Beta software can have bugs that affect data.