What is wasabi

wasabi is a low-code platform for building business applications. App builders define data, screens, and processes declaratively in a studio, and end users run the resulting apps in a runtime, with real-time collaboration, AI assistance, and a complete audit trail. No backend boilerplate, no glue code.

The idea

Building a business app the traditional way means writing a backend, wiring a frontend, and stitching workflows across both. wasabi collapses that into one declarative model: you describe your forms, data, and workflows once, as concise definitions and visual editors, then publish them. Everything you publish becomes an immutable, content-hashed snapshot with full provenance (who published it, when, and exactly which version), so every app is reproducible and auditable by construction.

Core building blocks

Forms

A form defines a data-entry screen and the shape of the records behind it, together with validation and layout. Fields can be text, numbers, money, percentages, dates and times, booleans, files, references to other records, nested groups, and editable tables. Each field renders through one of ~24 capture widgets (currency inputs, date pickers, dropdowns, reference pickers, editable grids, and more), and can opt into features like barcode scanning, geolocation, voice input, or AI-assisted filling. Forms can inherit and compose from one another, so shared field sets are defined once and reused.

Data sources, views & browsers

Data sources bring reference and tabular data into your app: inline tables, CSV/JSON/Excel files, or live collections. A view shapes and aggregates your live data with a pipeline, much like a view in a database: it filters, groups, and summarizes records into a derived, always-current dataset. A browser then presents a dataset to people as a searchable, filterable, faceted, sortable list with a detail view and custom actions.

Workflows

Workflows model your business processes visually with BPMN. The palette includes user tasks (a human fills a form), service tasks (automated actions), AI tasks (an LLM producing structured output), conversation tasks (a goal-directed, multi-turn chat that can use tools), sub-processes, timers, and message events, wired together with exclusive, inclusive, and parallel gateways. Workflows are durable and event-sourced: they survive restarts, wait on timers and external events, branch and run work in parallel, and persist their documents as they go.

Safe expressions

Anywhere a value can be dynamic, such as a field's label, whether it's visible or required, a default, or a validation rule, you write a short expression prefixed with =. These compile to a closed, safe expression language (no arbitrary JavaScript ever runs), with built-in functions like today, now, round, sum, count, and avg, plus cross-record lookups and table queries like =@data/rates.where(from == "USD").only.rate.

What you can build

wasabi is at its best for multi-step, auditable business processes:

• Procurement & purchase orders: capture requests, route them through multi-level approvals, and keep a permanent record of every decision.
• Invoicing & billing: model invoices with computed totals and tax, track payment status, and summarize with views.
• CRM: manage companies, contacts, and interactions with reusable, inherited record types.
• Inventory & warehouse: track stock across locations and drive picking, receiving, and reconciliation with workflows. (A full purchasing-and-sales warehouse system has already been built on wasabi.)
• Expense reports & reimbursement: collect expenses with validation caps, route through manager and finance approvals, and authorize payment.

Each of these leans on the same building blocks: forms for data, views and browsers for reading and reporting, workflows for the process, and expressions for the logic.

How it works

wasabi runs across three planes:

1. Author (studio). Builders create artifacts (forms, data sources, browsers, templates) as concise definitions, and design workflows in a visual BPMN editor.
2. Publish. A compiler validates everything, resolves cross-references, catches cycles, and emits immutable, content-hashed snapshots with full provenance. Those snapshots are deployed to the runtime.
3. Run (runtime). End users work in a catalog (browse and edit records) and an inbox (complete assigned workflow tasks, whether forms or AI conversations). Multiple people can edit the same record at once thanks to real-time collaborative editing, and operators watch live and historical process runs in a monitoring view.

What makes it different

• Auditable by construction. Every published version is content-hashed and archived, with provenance recorded.
• Durable workflows. An event-sourced engine that survives restarts and handles timers and asynchronous events.
• Safe by design. Expressions run in a closed evaluator; no arbitrary code executes.
• Real-time collaboration. Conflict-free multi-user editing on shared records.
• AI where it helps. Assisted form filling, structured extraction, and goal-directed conversation tasks.

Who it's for

wasabi is built for teams who need to ship business-critical apps quickly without giving up traceability: business analysts and app builders who want to move without backend overhead, and organizations running approvals, document workflows, and inventory or finance processes where an immutable audit trail matters.

Ready to go deeper? Core concepts covers views, browsers, message-driven processes, data transformation, and expression scope. More guides on authoring in the studio and working in the runtime are on the way.