isanna studio

What it is

Studio is the running instance of a launch platform: marketing, checkout, payment, accounts and automated delivery as hardened building blocks rather than per-product plumbing. The tools it serves are writing tools, but the engineering interest is the layer underneath them — fix the checkout webhook once and every product inherits the fix.

How it works

One app, many hosts

A single deployment serves the company site, the studio, and each derived storefront. Host-based routing decides which surface a request belongs to before a page renders.

Table-driven surfaces

A new storefront — its own domain, its own selected subset of tools — is one row in a surfaces table, not a new application. The tool set is resolved from that row, never hand-copied, so a newly registered tool can never be silently missing from a surface.

Fungible credits

Accounts hold credits rather than per-tool entitlements, so a purchase made for one tool is spendable on any other. Magic-link authentication, no passwords.

Provider-agnostic payments

The payment provider sits behind one interface with a second already wired to it, so the dependency is replaceable rather than load-bearing.

Chrome from one model

Header, footer and navigation come from a shared package driven by one declarative site model. A conformance suite runs inside this app’s deploy gate and fails the build on a hardcoded link, a raw colour, or a hand-rolled header.

What is true today

In service at studio.isanna.ai, with roughly thirty tools live and the derived-surface mechanism running in production.