Software · Developer and integration
Low-code platforms
Builders for forms, workflows and simple apps, so business teams make tools within guardrails IT controls.
Business teams want to build their own forms and trackers, and IT wants to avoid hundreds of unmanaged spreadsheets. We build low-code platforms, or configure existing ones, so staff can assemble forms, approval flows and data views from approved blocks while IT controls data sources, permissions and publishing. Anything beyond the blocks is extended with real code.
What we build
- Form and page builders that store each definition as a versioned JSON schema
- Visual workflow designers for approvals, notifications and data updates
- Connector libraries that expose only approved data sources to citizen developers
- Governance consoles for publishing, permissions and app ownership
- Power Apps, Appsmith or Budibase set-ups with custom components and plugins
- Code extension points where developers add reviewed logic beyond the builder
DemoInteractive · sample data
Try it live.
A working sample with made-up data. It runs in your browser; nothing is sent anywhere.
{
"form": "leave_request",
"version": 4,
"fields": [
{ "id": "type", "type": "select", "options": ["Annual", "Sick", "Unpaid"] },
{ "id": "from", "type": "date", "required": true },
{ "id": "to", "type": "date", "required": true },
{ "id": "reason", "type": "text", "showIf": "type == Unpaid" }
],What it does well
Approved blocks
Teams build with components and data sources that IT has already checked.
Definitions as data
Every form and flow is stored as versioned JSON, so changes can be reviewed and rolled back.
Publishing controls
Apps move from draft to live only after the owner and an IT reviewer approve.
Extend with code
Developers add custom components and logic where the visual builder runs out.
Ownership tracking
Each app has a named owner, a user list and known data sources, so none are orphaned.
Open exports
Definitions export in open formats, and self-hosted options keep data in your environment.
Questions
Should we buy a low-code platform or build our own?
In most cases, buy or self-host an existing platform such as Power Apps, Appsmith or Budibase. Building your own makes sense when low-code is part of a product you sell, when users need a builder shaped around your domain, or when existing platforms cannot meet data residency or licensing needs.
How do we stop low-code apps becoming a mess?
Governance from day one: approved connectors, separate draft and live environments, named owners and a review before publishing. We also keep an inventory of every app with its data sources and last use, so abandoned apps are found and retired.
What happens when an app outgrows low-code?
Because definitions are stored as structured data and business rules are documented, a developer can rebuild the app in code without guessing what it did. We flag apps nearing limits on users, data volume or complexity before they become a problem.