Knowledge base
Plain-language guides to describing, agreeing and looking after your business application.
No article matches. Try another word.
Start here
-
What LobLogix is, in plain words
A platform that produces the backend of a business application. You describe it, agree in writing what it will do, and it is built and checked against what you approved.
-
How LobLogix works
The steps from a first description to an application that has passed the checks you agreed and is ready to try.
-
What LobLogix builds, and what it doesn't
LobLogix builds the backend of a business application. The frontend, meaning the screens, is yours to choose and build.
-
What the alpha includes
What LobLogix delivers in its alpha, the limits you should know about, and what comes after it.
-
Getting started
Create your account, confirm your email, wait for company review, and create your first application.
-
Words you will meet
The words LobLogix uses on screen, each explained in one or two plain sentences.
Questions people ask first
-
Do I need to know how to code?
No. You describe, agree, review and try it in plain language, and LobLogix builds from what you agreed.
-
Do I need a technical person or an infrastructure specialist?
Not to start, not to get a built and checked application, and not to try it. You may want one for the frontend, and later for going live.
-
What do I need to get started?
An email address, your company's name and one sentence about what you want to build. There is nothing to install.
-
What makes LobLogix different?
You agree in writing what will be built, it has to pass checks you approved, and every later change follows the same path.
-
Can I use my own language?
You can write to the assistant in your own language. The workspace is in English, and we test in English.
Your account and company
-
Company review: what happens after you register
A person at LobLogix reviews each new company before its workspace opens. Here is what you see while you wait.
-
Signing in and passwords
How to sign in, reset or change your password, and what sign-in options are not available yet.
-
Applications: create, rename, archive
An application is one thing you are building. A company can have several.
-
AI usage and your monthly allowance
Your company has a monthly allowance for AI work. Here is where to see it and what happens when it runs out.
Describe and agree
-
Describe what you need
How to tell the assistant what your business needs, and what makes a description easy to turn into an agreement.
-
Agree the list
Before anything is written, you agree a numbered list of what the application will do, each item with a Done when sentence.
-
Review proposed changes
Every change to your specification is shown to you first. You apply it, pick parts of it, or reject it.
-
Change something later
Ask for a change in the conversation and see what stays, what changes and what is new before you agree.
-
Follow the work on Your Crew
Your Crew shows each piece of agreed work, what needs you, and lets you say when it is finished.
-
Read and edit your Living Spec
The Living Spec tab shows your application as a diagram with a side panel for the details, all in business terms.
Checks
-
Checks before the build
LobLogix writes checks from your agreed specification before the application is built, and you approve them.
-
Write, review and lock your checks
Ask LobLogix to write checks from your specification, review them, and lock them so nothing changes quietly.
-
How checks are run, and what a pass means
The application runs in a separate test space, and each check passes or fails by what the application actually does.
Versions
Running your application
-
Preview, Stage and Production
Three places an application can run. Preview to try it, Stage to sign it off, and Production for real use, which comes after the alpha.
-
How a release works: review, install, verify
Every version reaches Preview or Stage the same way. You review it, LobLogix installs it, and LobLogix confirms that it is running.
-
Build and deploy
Turn a version that passed into something running, install it in Preview or Stage, and open it.
-
Changes to your stored records
When a new version changes what you record, the stored records have to change too. LobLogix prepares that change, tries it first and stops anything that could lose information.
-
If a release goes wrong
LobLogix keeps the record of what failed and offers only the ways back that are safe. Sometimes that is the previous version, and sometimes it is a corrected one.
-
Health and logs on the Deployment page
Where each application runs, which version it is, whether it is answering, and what happened at each attempt. Every figure says when it was measured.
-
Ask My Backend: try your application in plain words
In Stage, add sample records, try what should work and what should be refused, and read what happened, all in plain words.
-
Build and connect your frontend
LobLogix builds the backend. The frontend is yours to choose, in any framework, built by you, your team, an agency or an AI coding tool.
-
Going live on your own infrastructure: how it is designed
Going live comes after the alpha. LobLogix is designed for production on machines your company controls, where by default LobLogix cannot access your production database.
Trust and security
-
Security and compliance, plainly
What protects your account, your work and your records, and what LobLogix does not offer yet.
-
If you pause your subscription
A live application is designed to keep working if your subscription stops. Here is what continues, what stops, and how long you have to come back.
Help
For technical colleagues
-
What a developer receives from LobLogix
For whoever builds the frontend. The connection points a built backend offers, how they are described, and how its users sign in.
-
The technology underneath
For technical colleagues. Elixir on the Erlang virtual machine, PostgreSQL, where an application runs and why it can move.