Apps are real code
Internal tools are real TanStack Start, React, and TypeScript projects, plus a Python and FastAPI runtime with a governed SDK. The durable asset is the project, not a saved canvas state.
Relpin builds internal tools as real TypeScript, React, or Python code edited in Studio with a governed SDK, instead of opaque configuration locked inside a visual builder.
deterministic source snapshot · sourceHash 7d47ab…bb2fb
Use visual assembly when an app is simple and low risk. Use a code-first model when the tool has to be reviewed, owned, and maintained by engineering over time.
Internal tools are real TanStack Start, React, and TypeScript projects, plus a Python and FastAPI runtime with a governed SDK. The durable asset is the project, not a saved canvas state.
Code is edited in Studio in a Monaco editor, builds with Vite, and deploys as isolated per-tenant Cloudflare Workers behind a fail-closed dispatch router. A container-backed live preview runs the app without sending secrets or database credentials to the browser.
The governed SDK keeps SQL, secrets, and connector calls server-side. Code is reviewed before it becomes a pinned release that can be promoted through DEV, TEST, and PROD.
All category guides for internal tool builders, AI agents, low-code limits, and production data.
Internal Tool BuilderThe core category page for governed internal tool building.
App BuilderThe product surface for building real internal apps in Relpin.
Low-Code Internal ToolsHow code ownership differs from low-code configuration.
Governed Internal ToolsHow code-first apps pass through governed releases.
Code-first internal tools are built as real source code rather than visual configuration. In Relpin they are TanStack Start, React, and TypeScript projects, plus a Python and FastAPI runtime, edited in Studio with a governed SDK.
Yes. Relpin supports governed AI authoring through OpenCode, which writes into the same real project. The generated code is still reviewable and still passes through the governed release path.