The brand stays bespoke
Nuxt and Vue continue to own layout, motion, accessibility, and responsive behavior.
Product platform · 2026
One platform.Three different stories.
Aurum standardizes what the customer never sees. Aurora lets teams edit exactly what the customer will.
A modular runtime, visual editor, and shared operating layer for a portfolio of real-estate websites.
How the model works Aurum 2.0
Three brands. One operating layer.
GGardenia
G95Genslera
P43Park 43
AuroraVisual editing
Content edited inside the final website
A
AurumShared runtime
liveData, permissions, plugins, and publishing
ContentPricingLeadsReleases
01
Bespoke brandsEvery website retains its own design
02
In-context editingAurora operates directly on the website
03
Shared operationsAurum connects data, roles, and publishing
01 — The premise
Reuse does not have to mean sameness.
Gardenia, Kamienica Genslera, and Park 43 each have their own visual language, information architecture, and enquiry journey. They still share the difficult operational work: content, units, pricing, publishing, permissions, and leads.
Operations become shared
One data source and the same safe publishing rules serve every project.
Capabilities become modules
Every domain evolves as a versioned plugin without rebuilding the administration product.
02 — Aurora Editor
Do not imagine the editor. Use it.
Select an element, change its copy, and publish a release. Aurora owns the draft and publication state while the website responds immediately.
G95+48 61 000 00 00
Restored architecture, contemporary comfort, and everyday life in the rhythm of the city.
Apartments 42–118 m²
03 — The system
A small core. An extensible product.
Choose a layer to see where platform responsibility ends and project freedom begins.
Scoped permissionsAtomic activationAudit trail
02
The core manages trust, not business logic
Identity, roles, sessions, the plugin catalog, audit, and observability form a stable control plane for every extension.
Scoped permissionsAtomic activationAudit trailIsolation · AI-assisted development
Generate code faster. Do not widen the trust boundary.
Plugins are designed as isolated units. AI-assisted code still has to satisfy the same explicit contract, receives only declared permissions, and cannot access another plugin’s data or processes.
AI can accelerate implementation. The architecture contains the consequences of a mistake.
Versioned manifest
The plugin declares its routes, permissions, and required capabilities.
Least privilege
Access is granted per capability, with no implicit trust.
Private data
Storage and migrations remain owned by the individual plugin.
Controlled activation
A candidate is verified before it can receive active traffic.
04 — Product plugins
Keep the core small. Let capabilities grow independently.
Aurum is not tied to one industry. Every plugin delivers a complete, isolated capability with its own API, data, permissions, and administration interface.
Visual editing for any Vue or Nuxt website without prescribing its layout or presentation model.
page.homehero.headlinehero.cta
draftreviewpublished
Plugin delivers
Visual editorDraftsLocalesPublishing
Permission scopecontent.*
Data ownershipaurora_content
05 — Safe change
A plugin updates like a product, not a file.
A candidate is validated away from active traffic. Only a complete version replaces the current one, while a failed activation preserves the last healthy state.
aurum-plugin-operatorIDLEValidate manifestSDK, schema, permissions
01Stage candidateRoutes and UI isolated
02Activate atomicallyCatalog promoted
03ObserveHealth, metrics, audit
04$
waiting for desired state…Outcome
The platform disappears. The capability remains.
Editors see the website, not a data model. Developers build the brand, not another admin panel. The organization gets one controlled way to operate content and inventory.
01
Editing directly inside the final layout
02
Drafts never leak into the public API
03
Roles derive from installed capabilities
04
A new project needs a scope, not a new CMS