App / Governed product surfaces

Apps with governed behavior.

Build websites, tools, dashboards, and product surfaces with routes, state, actions, publishing, and runtime checks that stay inspectable.

Scroll the conversation

When a page needs behavior, contracts take over.

Minora starts with the visible product surface, then layers state, data, requests, and QA so the app can be inspected and operated.

Surface: define the screens, routes, shell, sections, and user-visible states.
Contract: add state, form flows, request actions, and module boundaries only where behavior is needed.
Inspect: check links, style ownership, runtime modules, locale behavior, and console readiness.
Ship: publish a versioned app surface that can keep changing through governed patches.

What App can become

Routes and shell

Multi-page products use shared shells, stable routes, locale-aware links, and preview links that stay current.

State and modules

Tabs, drawers, forms, data views, charts, and interactions are described through contracts instead of hidden scripts.

Publish hardening

Minora checks links, styles, modules, runtime triggers, SEO, versions, and release readiness before the surface ships.

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

Build the app surface first.

Start with visible routes and screens. Add backend power only when the product needs it.

See pricing