Deployments
Opulent's abilities and limitations in publishing the deliverables it builds
Overview
Opulent can publish the deliverables it generates from scratch — small apps, reports, decks, dashboards, and shareable portals — so you can hand a live link to your team instead of a zip file. Every publish requires your approval, and you can roll back at any time. Opulent has more limitations when deploying pre-existing applications it did not build.
Deployments are Partial today. Publishing apps, reports, and dashboards that Opulent builds from its templates works now, with approval gating and rollback. Broader deck and portal targets, plus deploying pre-existing applications, are still rolling out.
| Component | New deliverables | Existing applications |
|---|---|---|
| Frontend | Supported out of the box (template) | Requires access via Secrets and Knowledge |
| Backend | Supported out of the box (API template) | Requires access via Secrets and Knowledge |
Frontend deployment
Opulent can publish frontend apps, reports, and dashboards using a pre-configured template built on Vite, TypeScript, Tailwind CSS, and Shadcn.
When you ask Opulent to create a frontend deliverable from scratch, it uses this template unless you specify otherwise. With your explicit approval, Opulent publishes the result to a live URL you can share, and you can roll it back if needed.
Backend deployment
For backend apps, Opulent uses an API template. As with frontend deliverables, Opulent can publish backend apps created from this template given your approval.
Limitations
- Pre-existing apps: Opulent is not equipped to deploy pre-existing applications. Frontend apps may work, but backend apps will not in most cases.
- Custom deployment: For deliverables not created with Opulent's templates, choose your own deployment method and provide the necessary credentials and instructions via Secrets and Knowledge.