Alpha · For the people who run the business or departments
Say what your business needs. Get its backend built, checked and running.
Describe it in plain words. LobLogix writes down what you agreed, builds the backend of your application, and checks it against what you approved before release.
Alpha. Access is subject to approval: we review each new company before opening its workspace.
Here’s what I’ll build — 3 capabilities. Have a read before you agree:
Take a booking for an item and a day Done when: a second booking for the same item and day is refused.
Move a booking through its steps Done when: it goes from requested to confirmed, collected, returned and closed, in that order.
Approve a discount Done when: a discount over ten percent waits for the manager's yes.
Change somethingAgree, don’t start yetAgree and build
An example: the list you agree before anything is built.
The backend is everything behind the screens: your records, your rules, who may do what, and sign-in. The frontend is yours to choose: React, Svelte, Vue, Flutter or anything else, built by you, your team, an agency or an AI coding tool.
For the moment a business tool has to be dependable
The spreadsheet five people edit, and nobody trusts.
The system only one person understands.
The quick AI-built prototype that customers now rely on.
It starts with rules like these, said in plain words. The kind of business does not change how it works.
RentalsAn item cannot be booked twice for the same day.
SalesA discount over ten percent waits for the manager's yes.
BillingAn invoice cannot be changed after it has been sent.
Field serviceOnly a supervisor can reassign a job.
How it works
1. Describe and agree
Write a few sentences. LobLogix asks questions, then lists what it will build, and each item ends with a “Done when” sentence. Your specification, the Living Spec, reads like your business: areas you can name, such as Bookings, Customers and Billing.
Screenshot to comeThe Living Spec
Your specification as a list of business areas, in your own words.
2. Approve the checks
LobLogix writes checks from your specification: things that should work, and things that should be refused. Nothing is built until you approve them. A version that fails them is not released, and the assistant's opinion cannot change that.
Screenshot to comeYour checks
Each check in plain language: what should work, and what should be refused.
3. Built, checked and tried
LobLogix builds the backend and runs it against your checks in a separate test space. In Stage, try it in plain words with Ask My Backend, or connect your own frontend. Then sign it off.
Screenshot to comeAsk My Backend
A request in plain words and its answer: counter staff ask for a twenty percent discount, and it waits for the manager's yes.
Afterwards you can show anyone three things, and nobody technical has to explain them: the checks pass, what changed since last week, and the version that is running.
Need a change later? Ask, see what it affects, agree. The same path runs again. Read the full walkthrough
Bring any frontend
Your backend speaks JSON:API, described in an OpenAPI document, and GraphQL, which carries its own schema. Developers and AI coding tools read both. It enforces sign-in and permissions itself, so no screen can get around your rules. In the alpha you connect your frontend to your application in Stage.
Your company provides the machines: virtual machines (VPS) with any provider, or your own bare-metal servers. LobLogix installs what the application needs on them.
Your data stays yours. By default LobLogix cannot access your production database, and the AI builds from your specification, not from your records.
Move it anywhere. It relies on no provider's own services, keeps your records in standard PostgreSQL, and does not depend on one AI model.
Built to stay up: a three-way database cluster, a hot standby cluster that can sit with a second provider, and continuous backups you can restore to a chosen moment.
LobLogix is a platform you keep building on, not a generator you use once.
In alpha. Here is what that means.
In the alpha
Everything your specification can express: records and how they link, calculated values, rules that refuse a bad entry, steps and approvals, roles, and sign-in. It runs in Preview and Stage on LobLogix hosting, with test records. You can connect your own frontend to your application in Stage, and try it in plain words with Ask My Backend.
Not in the alpha
Production, with its backups and high availability. A workspace in languages other than English. A formal security certification. If your specification asks for something the alpha cannot build, LobLogix tells you.
After the alpha, by design
Going live on infrastructure your company controls, on the business tiers. If your subscription stops, a live application keeps working, without changes, monitoring or security fixes.
No. You describe, agree, review and try it in plain language. The frontend is a separate job: build it yourself with an AI coding tool, or have a developer or an agency do it.
Do I get a finished app with screens?
You get the backend, built and checked. The frontend is yours: build it in React, Svelte, Vue, Flutter or anything else, yourself, with your team, an agency or an AI coding tool, and connect it.
Can the assistant change things without asking me?
No. Changes arrive as proposals you apply or reject, and you can stop the assistant mid-way.
Will AI costs surprise me?
Your company has a monthly AI allowance, and AI work pauses when it is used up. Before it rewrites your specification from a request, LobLogix reads back what it is about to do and waits for your yes.
Is LobLogix certified, for example SOC 2 or ISO 27001?
No, not today. If your purchase requires a certified supplier now, LobLogix is not yet the right choice.
What happens if we stop paying?
We would rather you stay because LobLogix keeps earning its place. If your subscription stops, a live application is designed to keep working, but changes, monitoring and security fixes stop. You can come back within three months. After that, we cannot promise your application still fits the platform. Going live comes after the alpha.