---
title: "Known limits"
description: "What dply doesn't do yet, what can change, and how to tell us what you find."
---

dply is generally available: sign-up is open, every plan is live, and you can run production apps on it. This page lists the gaps you may still run into, so you can plan around them before you hit them.

## Known limits

- **Supported stacks.** Python, Go and WordPress apps can't be deployed. See [Frameworks & runtimes](/docs/frameworks#not-supported).
- **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 can change

- **Features and interface.** Pages, labels and defaults change between releases. These docs are updated as they do, and the [Changelog](/docs/changelog) lists what changed.
- **Prices.** Plan prices and usage rates are on [Plans & pricing](/docs/pricing), and any change to them is listed in the [Changelog](/docs/changelog).

There is no service level agreement on the self-serve plans. [Contact us](mailto:hello@dply.io) about Enterprise terms.

## 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](mailto:hello@dply.io) from the address on your dply account. To report a vulnerability, email [security@dply.io](mailto:security@dply.io) instead. See [Support](/docs/support) and [Report abuse](/docs/abuse).

## Your data

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](/docs/paused-accounts).

> [!TIP]
> Keep your own backups of anything you can't recreate, on any hosting platform.

## Related

- [Quickstart](/docs/quickstart)
- [Plans & pricing](/docs/pricing)
- [Support](/docs/support)
- [Changelog](/docs/changelog)