wrenlyDocumentation
Reference & direction

Capabilities & roadmap

Understand what is implemented, what is in development and what comes next.

Roadmap entries describe direction. They are not controls available in the workspace, and individual features do not have promised delivery dates here. Wrenly is available as an open-source public beta.

Implemented workflows

Implemented · release checks continue
CapabilityWhat you can doLearn more
Next.js and Laravel13Generate, edit, validate and preview revisionsConversations
Durable executionReload and resume viewing saved progress and resultsBuild lifecycle
Teams and sharingInvite members and grant per-project Viewer/Editor accessProjects
Models and SkillsSave supported provider connections and pin guidance versionsModels, Skills
Private publishingPromote a sandbox-built image through a private registry to CoolifyPublishing
Drafts and archivesSave ideas before building and retain archived project historyProjects

Implemented means the code path is connected. It does not replace fresh-install, upgrade, security or real-provider acceptance for a release.

In development

In development · Production workflow pending

Experimental generated-app databases: Development has an explicit opt-in workflow for resource setup, saved build selection, reviewed backups/migrations, a role-aware viewer and isolated previews. Production database provisioning and database-backed publishing remain unavailable. Development resources are not promoted implicitly.

Understand the database boundaries and current status.

Planned direction

Planned
  • More frameworks: Vue and Django, following the same generation, validation, revision, preview and publishing requirements.
  • MCP connectors: Figma and other tools that bring development context into a project.
  • Provider choice for source and deployment: additional Git and deployment adapters, beyond the current Gitea/registry/Coolify path.
  • Richer teamwork: further collaboration capabilities beyond current invitations, sharing, shared drafts and attributed project conversations.
  • Explicit tool permissions: reviewable capabilities for tools such as model browsing. Preview media permissions currently allow exact image/video hosts; they do not enable model browsing or grant sandbox network access.

Keep the boundaries clear

Instance dataControl PostgreSQL · active
Generated-app dataExperimental · Development only
These are separate resources and credentials. Generated applications never receive control-database access. Development uses its own scoped credentials; Production provisioning remains unavailable.

Instance PostgreSQL stores Wrenly's own records. Generated-app PostgreSQL is a separate module in development; it never shares the instance database credentials.