Skip to content

Examples

Real apps you can open and copy

These examples live in the Protobase repository and docs, with their code. The ERP and the real estate app are also starting points in Protobase Cloud, and the property portal runs as a live demo.

Start in the cloud

Early accessSign up with GitHub or email. Your first app is live in a few minutes. Plans from €0.99 a month.

Or self-host it for free
A repair record with sections for the bike, the workshop and the money, and buttons for Ready for pickup and Collected and paid.
Repair R-303, with its buttons.

Docs guide

Pip’s bike shop: a back office on a table you already have

  • Two tables, customers and repairs. A booking site writes the repairs; the front desk and the workshop work in the admin.
  • Filters for the questions the front desk asks most, a chart of bookings, and a record page laid out like the paper repair card.
  • Buttons for the moves the shop makes all day, and a view for the mechanics without the money columns.
  • One firm rule in the description: a bike leaves the shop paid.
A sales overview page with counts of draft orders, unpaid deliveries, overdue invoices and open leads, the biggest unpaid delivery, and lists of invoices and orders.
The sales overview.

Docs guide

Veldhuis Supply: one page that says what needs attention

  • Sam runs sales and wants one page: four numbers, the lists behind them, one order to chase, and the leads, with a way to add one.
  • It is a composed page: JSX that compiles to plain data, with no endpoints and no React to maintain.
  • Every block reads the regular API with Sam’s token, so the access rules apply exactly as on the lists.
A billing page with the current plan and seats, billing details, payment cards and invoices.
A billing page an app gives its own customers, from the docs.

Docs guide

Northwind Labs: a billing page inside an app

  • Ada handles billing, and gets one page for it: the plan, who is billed, how they pay and what they paid.
  • It is a composed page too, with forms in a dialog, buttons that act on records, and one component written in React.
The orders list of the ERP example, with a chart of orders per day, filters and a sidebar grouped into sales, inventory, finance and admin.
Orders in the ERP.

Preset

An ERP for an industrial supplier

  • 19 resources across 6 schemas, including a legacy hr."EMP_MASTER" table, and 8 roles, from sales and the warehouse to the auditor.
  • A sales overview page, an API function, a nightly job on Amsterdam time, organizations, cost fields only some roles may read, and a bottom bar for the warehouse on phones.
  • Two organizations, Dutch, German and English companies and three years of history. The largest seed holds 10,000,000 stock moves.
A tenant record with name, email and a revealed IBAN, and the homes the tenant rents.
A tenant, with the IBAN revealed on request.

Preset

Rental and property management

  • Owners, properties, units, leases, tenants, rent, payments, arrears and maintenance, with Dutch data: 19 resources and 4 roles.
  • A portfolio overview page. Tenants’ IBANs are revealed one at a time, with an audit record.
  • Overlapping leases are refused by a database constraint. The largest seed holds 10,000 properties, 107,000 units and 3.57 million rent charges.
A public portal with homes for sale shown as cards with photos, prices and energy labels.
The portal, as visitors see it. The demo resets every day.

Live demo

A public property portal

  • Homes for sale and for rent in the Netherlands and Spain. Visitors browse without an account; anyone can sign up.
  • Members keep favorites, private notes and saved searches that email new homes at once or once a day.
  • Photo carousels with resized images and placeholders, and a map with approximate positions. The largest seed holds 100,000 listings and 433,000 photos.

Keep reading

Your back office, live in a few minutes

Sign up with GitHub or email, pick a starting point, and ask the assistant for what you need.

Start in the cloud

Early access Plans from €0.99 a month.