The low-code Java framework for AI-assisted development

Write what makes your business different. Wercbanc does the rest.

Your developers and their AI write only the business logic. Wercbanc generates the rest from a plain-text model: entities, rules, lifecycles, forms, grids and pages, in plain Java you own.

Wercstat ERP, built on Wercbanc: a sales order and the list of sales requests
Wercstat ERP, built on Wercbanc: a sales order and the list of sales requests.

From a design brief to a running application. All of it text.

A change to a Wercbanc application is one cycle. You write the brief, you and your AI write the design, your AI implements it in the model and in Java, and Wercbanc generates the application. Every step before the running screen is a file in Git.

  1. You

    Design brief

    What the feature must do, in a few paragraphs of Markdown.

    • orders-design-brief.md
  2. You and AI

    Design

    The design document: the concept, the decisions and the open questions. Your AI drafts it against the code as it stands; you review and decide.

    • orders-design.md
  3. AI

    Model and business logic

    The entities, rules, lifecycles, forms and grids declared in Werc; the business logic in plain Java.

    • Order.werc
    • OrderService.java
  4. Wercbanc

    Application

    The generator turns the model into Java, Spring Boot and Vaadin: persistence, pages, forms and grids, ready to run.

Round again: refining the feature starts from the design, with the model that is already there.

How a Werc model becomes an application →

The best assistant your AI could ask for

AI writes code fast. Keeping it consistent is the hard part.

Everything, from the design notes to the running application, is text in Git: the model, the generated code, the business logic and the documentation. There is no visual designer and no metadata database in between, so your coding agent reads, changes and reviews the whole application with the tools it already has.

Wercbanc splits the work. The generator produces the persistence, the actions, the forms and the grids from the model, deterministically, every time. None of that needs to be read: the model already says what it does, in a few lines per entity.

So your AI’s context holds the problem, not the plumbing. It reads and writes the model and the business logic, the two places where judgement matters, and a reviewer reads every change in a diff.

SalesOrder.werc
    // Delivery    attribute OrderDateTime deliveryFromDateTime deliveryFromDateTimeLabel mandatory    attribute OrderDateTime deliveryToDateTime   deliveryToDateTimeLabel   mandatory    relation  Country       finalDestination     finalDestinationLabel    // Terms    relation TermsOfPayment  termsOfPayment  mandatory    relation TermsOfDelivery termsOfDelivery mandatory    relation DeliveryAddress portOfShipment     portOfShipmentLabel    relation DeliveryAddress portOfDestination  portOfDestinationLabel    relation DeliveryAddress placeOfDestination placeOfDestinationLabel
This is the whole change a reviewer reads. The forms, the grids and the persistence follow from it.
Wercstat

Your custom ERP starts here.

Start from the modules of Wercstat ERP, built on Wercbanc. Take the ones your business needs, extend them with your own business logic, and model only what makes your business different.

Trade

Quotations, sales and purchase orders, consignments, deliveries and invoices.

Warehousing

Every unit of stock is tracked individually, with its own specification, price, history, cost buildup and location.

Accounting

General ledger, accounts receivable and payable, VAT, bank statements, payments and cost units.

Also: production and quality, workshop, transport and workflow. Every module is optional.

Why teams choose Wercbanc.

Wercbanc is a low-code framework for Java teams and their coding agents.

One model, always regenerated

Entities, validation, lifecycles, forms, grids, pages and menus come from .werc files. Change the model and regenerate: nothing is maintained twice, and your hand-written code is never overwritten.

Built for AI to work on

Everything is text and lives in Git, so your coding agent can read, change, diff and review the whole application. The generator handles the plumbing deterministically; the AI works where it is strong. A maintained skill pack for coding agents ships with every release.

Code you own

The output is plain Java, Spring and Vaadin in your own packages, with no licence header.

Why you are never locked in →

A running start

The modules every business application needs are included, so the first sprint goes to your domain, not to users, rights and locales.

See what is included →

No lock-in

Your business logic stands on an open-source foundation.

Your entities, their generated repositories and the services that act on them depend only on the Apache-2.0 wercbanc-domain libraries, Spring Boot and JPA. If you stop using Wercbanc, that code keeps running: declared rules are still enforced, rows are still scoped to their tenant and audited, temporal validity is still checked.

How the open foundation works →

Without the frame you supply three standard Spring and Hibernate pieces: a tenant resolver, an auditor and the transaction around each unit of work. Screens, view models and access control belong to the commercial frame and do not come along.

Standard modules

The parts every business application needs, already built.

Wercbanc ships with standard modules, with entities, services and pages, released with the framework at the same version.

Access

  • Users, groups and rolesUsers, user groups and roles, with their pages
  • AuthorizationAccess-control entries per object, enforced on the server
  • Multi-tenancyEvery row is tagged and every query is filtered; your application contains no tenant code

Attachments

  • RevisionsEvery upload is a new version; older ones are kept and can be restored
  • Folders and tagsA folder set and a coloured tag set per entity type
  • AI summaryA summary of a document and a description of an image, written by the chat agents
  • Scan and quarantineA file that fails the scan never leaves the store

Locales and time zones

  • CountriesEach with its currency, language, region, unit system and telephone prefix
  • Currencies and languagesReference tables your model relates to
  • Locales and time zonesThe locales and time zones users and records are tied to
  • Seeded per tenantEUR, English, the EU and Europe/Amsterdam on first start; the rest on the pages

AI

  • LLM moduleModels, agents, prompts and personas, tools and skills, MCP servers, vector stores
  • Page assistantA chat the application adds with one dependency; it reads and operates the open page with the user's own permissions, and every action waits for the user's confirmation

Written in Werc, like your application, and you can read their models.

Standard modules in the manual →

In development and in production since 2008.

  1. 1996Van Kessel IT starts customizing ERP systems
  2. 2008The framework's first production system goes live: a trade ERP, still running
  3. 2021Web generation: Spring Boot and Vaadin
  4. 2026The Werc language and Wercbanc as a product

Wercstat ERP, trade and production

300+
entities in one production system
24/7
including night shifts, integrated with Baan IV
1,922
.werc model files
10,500+
commits

Wercbanc is the framework behind Wercstat ERP, in production at Euramax Cladding. wercstat.com →

Is Wercbanc for you?

A good fit

  • Large, consistent administrative systems: ERP, supply chain, finance, operations, back-office SaaS.
  • Java teams who want generated plumbing and plain code, not a visual designer.
  • Teams that already work with coding agents, or want to.
  • Multi-tenant SaaS without writing tenancy yourself.

Not the right tool (yet)

Free for development. Talk to us about production. Talk to us →

Ready to take a closer look?

Read the docs, or talk to us about evaluating Wercbanc.