Internal tools deserve better than a black box.
Every company runs on tools nobody outside it will ever see: the refund desk, the inventory view, the approval queue. They are built in a hurry, owned by nobody, and replaced every few years. Partials exists to make them fast to build, safe to run, and worth keeping.
What we believe
- The code is the product
- A visual editor is a faster way to write software, not a replacement for it. Everything Partials produces is readable TypeScript you can review, extend, and keep.
- Trust is the default case
- Internal tools touch the most sensitive data a company has. Permissions, audit, and credential handling are built in, not sold separately.
- Explicit beats magic
- Editing and releasing are different actions. Removing a component asks first. Nothing changes in production because someone opened an editor.
- Everyone at the table
- The best internal tools come from the people who use them every day, with engineers reviewing rather than rewriting. Partials is designed for that hand-off.
How Partials is built
Three services, one protocol. A Go API that owns authorization, credentials, and the app repository. A React client with the editor and the app runtime. A Node runtime that executes server-side code in isolated workers, with no secrets in the process.
Go API
Authorization, resources, queries, audit, source control, and the served app.
React client
Workspace, visual editor, and the renderer that runs published apps.
Node runtime
Supervised workers for JavaScript queries and transformers, reached over gRPC.
MySQL
The only external dependency. Everything else ships in the image.
Talk to the people building it.
We are a small team and we answer our own email. Tell us what you are trying to build and we will tell you honestly whether Partials is the right fit.