Frontend rendering infrastructure / AI agent era

Build the interface AI can ship.

Minora turns AI output into composed, inspected, versioned, and publishable web surfaces.

Choose a surface View flow

Image placeholder

IntentPreviewPublish

Intent becomes interface.

01 / Choose

What are you trying to make visible?

Start from the result you want. Each path keeps the same Minora loop: describe, preview, point, revise, and ship.

Docs

Turn a conversation into a readable brief, report, launch note, or decision page.

Shape a document 02

Canvas

Turn fragments into a movable map, option board, diagram, or product shape.

Map the idea 03

App

Turn intent into a routed, stateful, publishable product surface.

Build the surface

02 / Flow

Intent becomes interface while the stage stays fixed.

A conversation is captured, drafted into a surface, patched with intent, checked in preview, and released only when the result is clear.

Prompt: build a site that explains what Minora makes possible.

01 / Prompt

Make this idea visible. I need a page, not a mockup.

Minora keeps the intent attached while it composes the surface.

02 / Controlled change

Compose structurePatch with intentVerify the surface

Each revision lands as a readable change instead of replacing the whole page.

03 / Surface

Published page

HeroFlowExamplesCTA

Preview route

The page is checked as a real surface with shared shell, locale content, links, and runtime behavior.

QA / locale / shell / runtime

Approved version

Only the reviewed version becomes the public site, while the next conversation can continue from the same structure.

reviewed / versioned / ready

Result: a page users can inspect, revise, localize, and ship.

Intent / define the goal
A rough request, image, or note enters Minora as visible intent, not as a finished black-box page.
Draft / compose the surface
Minora composes structure first: sections, shell, routes, copy, media, and the shape of the final surface.
Patch / keep changes precise
Feedback becomes a precise patch against the part that should change while the rest of the page stays stable.
Preview / verify before release
The result is checked as a real route with shared shell, links, locale content, layout, and runtime contracts.
Publish / ship the approved version
Only the reviewed version becomes the public surface.

Intent stays visible.

The surface stays structured.

Release stays governed.

A safer editing loop

Freedom needs a safe boundary. Minora gives AI that boundary.

Minora does not assume AI will never be wrong.

It gives each change a boundary, a preview, and a versioned result, so mistakes are easier to see before they become the published page.

See how Minora compares

03 / System

AI can draft. Minora makes the surface controllable.

The product is an authoring plane for structure, preview, version history, release boundaries, localization, and public delivery.

Inspectable page structure
Point-and-patch revision
Shared shell and locale control
Versioned release boundary

04 / Capabilities

A release path for agent-built frontends.

Compose

Turn intent into a structured page surface with sections, layout, copy, media, and motion contracts.

Preview

Inspect visible changes before they become the page users see.

Version

Keep interface history readable instead of shipping a black-box generated artifact.

Publish

Release the approved version with shared layout, links, locales, and production boundaries intact.

05 / Example

A single campaign moves from canvas to docs to site.

Sample only: Hoshinogawa Hanabi Festival is a fictional event made to show how one Minora conversation can become a canvas, a planning document, and a public page.

01 / Canvas

Map the fictional fireworks campaign: audience, scene, assets, risks, and decisions stay visible on one working surface.

Open canvas example

02 / Docs

Turn the canvas into a structured launch brief with timeline, audience logic, operations notes, and disclosure requirements.

Open docs example

03 / Site

Publish a fictional Japanese-style festival page with poster-like hierarchy, schedule, access copy, and clear sample status.

Open site example

Install before signup

Connect Minora to Codex or Claude.

Add the MCP server first. When the agent needs access, Minora opens a browser flow so the right user can sign in or create a workspace.

Create a workspace

Claude Code

For Claude Code remote MCP.

claude mcp add minora --transport sse https://app.minora.dev/mcp

Codex

For Codex CLI and the Codex desktop app configuration.

mkdir -p ~/.codex && touch ~/.codex/config.toml && { grep -q '^\[mcp_servers\.minora\]' ~/.codex/config.toml || printf '\n[mcp_servers.minora]\nurl = "https://app.minora.dev/mcp"\n' >> ~/.codex/config.toml; } && codex mcp login minora

06 / Ship

Every change becomes a controlled surface.

Minora gives AI-generated interfaces a place to become real: authored, reviewed, versioned, and released.

Start with Minora