Deployments, Versions & Rollback
Every time you deploy, DYPAI creates a new version of your frontend. The active version is what your users see. Older versions stay available so you can roll back instantly if something breaks.
Deployment history
Open the Frontend tab in your project dashboard. The deployments list shows every build, newest first, with:
- Version number — increments on every deploy (
v1,v2,v3…) - Status —
active,ready,building, orfailed - Created at — when the deploy was triggered
- Size — total output size of the build
- File count — how many assets were produced
Click any version to see its build logs, file list, and the exact commit (if deployed from Git).
Build logs
If a deploy fails, open its logs to see what went wrong. Typical issues:
- Missing dependency in
package.json - Build command failed (
npm run buildexited with error) - Output directory not found (DYPAI expects
dist/,build/, orout/depending on the framework) - Environment variable required at build time but not set
- Exceeded 10-minute build time or 50 MB output size
Build logs are kept for the last 50 deploys per project.
Rollback
Broke production? One click gets you back.
Find the version
Go to Frontend → Deployments and find the last version you know was working.
Click Rollback
Click Rollback to this version next to it. Confirm the prompt.
Instant switch
The active version switches immediately. No rebuild, no waiting — the old build is already cached at the edge. Usually live within seconds.
Rollback is not destructive
Rolling back doesn't delete newer versions. You can roll forward again to any version at any time.
Compare versions
Click two versions to see the difference in size, file count, and which files changed. Useful for diagnosing why a build suddenly doubled in size or lost assets.
Automatic health checks
After every deploy, DYPAI verifies the new version responds with a 200 status. If it returns a 500 (build artifacts missing, bad routing, etc.), the deploy is automatically retried. You don't need to intervene.
Deploys that stay broken after retries are marked failed and the previous active version keeps serving traffic.
Download source
You can download the full source of any version as a ZIP:
- Dashboard: Frontend → Deployments → (version) → Download source
- Use case: recover code after a lost local copy, audit what was actually deployed, or pass the ZIP to a collaborator
Limits
| Versions kept | Last 50 per project |
| Rollback window | Any version in history, as long as it's still stored |
| Build logs retention | 30 days |
Older versions are automatically garbage-collected after 50 deploys to keep your storage usage reasonable.