This article explains what Schepta is, the problem it solves, and the space it fills. Why I chose an open source library over a microsaas — and why I haven't (yet) bet on AI agents that resolve tasks autonomously — is the topic of the next article in the series.
What it is and what problem it solves
Schepta is a tool that turns an interface description — in JSON format — into real screens and forms, without having to write each screen by hand in code. That description can be interpreted in React, Vue, or plain JavaScript, depending on the project.
The problem it helps solve shows up when the interface depends on many contexts: multiple clients (multi-tenant), multiple flows, A/B tests, or when the backend — or even AI tools — define what should appear on screen. In those cases, writing and maintaining each variation in code becomes chaos. Schepta centralizes the screen definition in a single format (the schema); a single engine interprets that format and generates the interface. Those using Schepta can focus on business rules and on defining what to show in each context, instead of the implementation details of each variation.
Why Schepta exists — the space it fills
Schepta exists for scenarios where you need the interface definition (what to show, in what order, with what validations) to be treated as data — a schema that carries UI semantics, not just data validation. It was designed to be framework-agnostic: the same schema works in React, Vue, or plain JavaScript. The core is lean and extensible, with sensible defaults you can swap out when needed. And the entire flow was built for server-driven or context-driven UI — for example, one schema per client or per tenant — not just for fixed forms defined at build time.
If this space makes sense for your project, Schepta is an option. The choice between Schepta and other tools depends on the needs of each project and team; what matters is that this space exists and that Schepta is here to fill it.
If this problem sounds familiar, the guide, documentation, and examples (React, Vue, and Vanilla) are at schepta.org.
Have you ever dealt with this chaos of forms that change per client, A/B test, or backend? How did you solve it?
Next step
In the next article in the series I talk about why I didn't take the common path: an analysis of the current moment in software development, what many devs are doing (microsaas, AI agents, and agentic automation) — and why I chose an open source library, without SaaS and without betting (yet) on agents that resolve tasks autonomously.
Top comments (0)