Roadmap

Atelier's direction is deeper convergence: one declared catalog, one rendering layer, one access model, and authoring ergonomics that make declaring an application as fluid as describing it. These are the themes we are investing in. They describe direction, not commitments or dates.

One catalog, one renderer

We are consolidating every building block — entity types, widget kinds, action shapes, view kinds — into a single, discoverable catalog, and routing every surface (admin dashboards, embedded analytics, portal pages) through the same rendering layer. The goal is that adding a new kind of block makes it immediately available everywhere, with no special cases.

Richer surface composition

Surfaces are gaining more expressive layout — nested grids, composable sections, and a growing library of widget kinds — so complex dashboards and detail pages can be assembled entirely from declarations, with live preview throughout.

Live template-to-tenant propagation

Today a tenant is created by forking the template into an independent copy, and then evolves on its own. We are designing a supported channel for propagating template-level improvements to tenants after the fork — with clear, opt-in control over how local customizations are preserved — so a fleet-wide improvement can reach every tenant without overwriting the changes a tenant has made.

A unified access and identity model

We continue to converge authorization onto a single, declarative source of truth driven by organization membership and roles, so access policy stays simple to reason about, consistent across every surface, and fail-closed by construction.

Authoring and developer experience

We are bringing the ergonomics of our sibling platform, Martha, to Atelier: a first-class command-line workflow with machine-readable output designed for both people and AI assistants, validation that runs in continuous integration so a malformed declaration is caught before it ships, and guardrails that flag conflicting declarations at author time rather than at runtime.

Compounding cleanups

Alongside the headline themes, we keep paying down the small inconsistencies that compound — tightening the notification model, hardening the delivery of background effects so nothing is silently dropped, and sharpening the boundaries between the data, execution, and surface planes. Each cleanup makes the next capability easier to add.