What LobLogix builds, and what it doesn't

LobLogix builds the backend of a business application: everything behind the screens. The frontend, meaning the screens people click on, is yours to choose and build.

What the backend is

• The records you keep. Customers, bookings, stock, invoices, visits, memberships: whatever your business tracks.
• How they link. A booking belongs to a customer, and a customer has many bookings.
• Calculated values. Totals, counts and averages, worked out for you.
• What people can do. Add, change and remove records, and actions of your own, such as approving an invoice.
• The rules they follow. A booking cannot overlap another. An amount cannot go below zero.
• Steps and approvals. A record moves through named stages, and some steps need a second person.
• Who may do what. Roles decide who can see, add, change or approve each kind of record.
• Sign-in. For the people who use your application.
• A connection point. Screens and other tools use it to read and change the records, within the rules.

The frontend is yours

Screens, forms and reports that people look at are the frontend. You choose the framework, such as React, Svelte, Vue or Flutter, and who builds it: you, your team, an agency or an AI coding tool. It connects to the backend through the connection point. See Build and connect your frontend.

You do not need a frontend to try it. In Stage you try the application in plain words. See Ask My Backend: try your application in plain words.

A good fit

Tools a business relies on for years: operations, bookings, stock, billing, customer and supplier records, approvals.

Not a good fit

• A marketing website.
• A quick experiment you may throw away next month.
• A need that a ready-made product already covers well.

When it cannot build something

If your specification asks for something the alpha cannot build, LobLogix tells you. It does not leave it out quietly.

See What the alpha includes.