Teams building business apps
SaaS products, internal tools, portals and sites with accounts, data and permissions.
What is VowCode?
In a usual project someone — today often an AI — writes controllers, data access code, permission checks, an API client, queues and jobs, and a person has to review all of it. In VowCode you describe what the system is and what each function may do. The platform builds the rest, so there is about ten times less code to review, and many kinds of bugs cannot be written at all.
Tables, fields, relations and who may see or change them — per table, column and row — in one model file.
Business rules are short VowCode functions. Each one starts with a header: who may call it, which data it may read or change, what comes in and what goes out.
The compiler checks the code against its header and generates the server code, SQL, the REST API with OpenAPI, realtime events and the JavaScript client.
Names come from your business — here in English, but they can be in any language. Keywords are icons:
For a security review, the header is enough: the body cannot reach anything the header does not list.
⚙️AddLabel
👥 Member
🔑 ✏️: 🗄️.TaskLabels
🔑 🔓: 🗄️.Labels
📥 Task: 🆔, Label: 🆔
📤 Labels: 🔢, Private: 🔢
{
🗄️.TaskLabels ➕ (Task = 📥.Task,
Label = 📥.Label)
↩️ (Labels = #🗄️.Labels,
Private = #🗄️.Labels 🔍 (Private))
}
SaaS products, internal tools, portals and sites with accounts, data and permissions.
Agents write the code; people check short headers instead of reading every line.
When code comes from contractors or AI, the header shows exactly what it can touch.
VowCode is in active development and runs today on .NET and SQLite. It will be released under a dual license: GNU AGPL-3.0 or a commercial license from Outsourcing Software Development EOOD.