Hosted for you · kept apart from others
Your company gets its own stand
You subscribe. We run the software. Your documents live in a database that no other company shares. When you change how the stand works, Lifecycle Portal is the desk: Development, Test and Production, the package library, backups, who may sign a release, and the credential your pipeline uses. You try it on Test, two people sign it off, then it goes to Production. Office work is in the browser. Developers can also use Visual Studio Code. Sales reps and the warehouse use the Android app — same company, same documents.
SaaS
You do not install servers on Friday night. Hosting, upgrades, backups and support are in the subscription.
Yours alone
Your stand is its own process and its own database. A neighbour's busy day does not take yours down. Nobody else's invoices sit in your tables.
DevOps
Lifecycle Portal is the desk: Development, Test and Production, packages, backups, people and CI. A change is packed, tried on Test, signed by two people, then Production.
Your stand
You are not mixed in with other customers
This is not one big database with a company column. Your stand is a separate process and a separate database. People open it on your own address, over HTTPS.
Your own process
The application runs for you. A neighbour's restart is not yours. Their peak load does not steal your CPU.
Your own database
Documents, lists and balances live in a database that is only yours. There is no shared table and no tenant-id column pretending they are separate.
Your own address
People sign in to your company, not to a shared workspace. The address is yours; HTTPS is on the way in.
Your data
Your books are not in someone else's cupboard
Kept apart is the first protection. On top: HTTPS on the way in, a snapshot before an upgrade, backups in the subscription, and an export you can take with you.
HTTPS to your stand
The browser, the Android app and the developer tools talk to your address. They do not land in a shared pool.
Jobs stay on your stand
Scripts, compilation and background jobs run inside your process. They never run against another company's database.
A restore is only your data
A snapshot, a backup or an export is of your documents and your configuration. Another company is not in that file.
Snapshots, backups, a way out
An upgrade takes a snapshot first and can go back. The subscription includes backups. You can export data and configuration whenever you want.
Lifecycle Portal
Write it, try it, then put it live
Lifecycle Portal is the desk for the stand: Development, Test and Production, the package library, backups, who may sign a release, and the credential your pipeline uses. You pack a change as a .zulopkg file, install it on Test, mark it Ready (two different people), then release it to Production. A pipeline may upload and install on Test. A person still marks Ready — no CI scope does that.
- 01
Write
On a Development stand the workspace is open. You save a file; the stand picks it up in a few seconds.
- 02
Pack
Upload a .zulopkg. The portal checks every file against the list inside the package before it keeps it.
- 03
Try it
Install on Test. Empty, or a copy of Production with mail and outbound jobs switched off so it cannot write to customers.
- 04
Sign off
Production takes only a package marked Ready. Two different people must press that. One person is not enough.
- 05
Go live
Release the Ready package. Production is not a sandbox: there is no rebuild-or-delete button on the live stand.
People and a two-person rule
An Owner invites by e-mail. Owner, Release manager, Developer, Viewer. Ready for production is a second person, not the uploader, unless the tenant turns that rule off.
Production, Test, Development
Production is live and has no rebuild-or-delete button. Test proves a package. Development is the workspace. The plan caps how many stands sit beside Production.
Backups you name, snapshots we take
Back up now on any stand, Production included. Restore onto Test or Development only. Zulo also snapshots before an upgrade or an install; those copies do not eat your library limit.
Updates try Test first
A platform update snapshots the stand and rolls back if it does not come back healthy. Production tells you to update a Test environment first and run the tests there.
CI uploads. A person signs off.
A credential can upload a package and install it on Test. GitHub Actions can sign in with no stored secret. Ready for production stays a person's button.
Logs and tests on the stand
Logs stay readable when the stand is stopped. Run tests on an environment: a run rolls back what it writes. After a Production platform update, Ready packages are installed on Test again before the next Release.
The portal is on the Business and Enterprise plans at lcp.getzulo.com. A smaller plan still has the stand; the full Test–Production cycle, people, backups and CI credentials are on those two plans. The portal itself is in English.
Open Lifecycle Portal at lcp.getzulo.com →
The Lifecycle Portal handbook — ship, Test, backups, people, CI →
Where you write
In the browser. Or in Visual Studio Code.
The business layer is files: JSON for the objects, C# for the scripts. You edit them in the stand's web editor or in ZuloOne Studio for Visual Studio Code. A save is on the stand in a few seconds.
In the browser
The editor is in the stand. Handlers, postings, commands and services open next to the object they belong to. For a small change you do not install a toolchain.
ZuloOne Studio for VS Code
Application Explorer, designers for lists, documents and registers, and C# next to the JSON. Connect to Environment downloads a mirror of the stand's files.
Same files, two desks
A save in the browser and a save in Studio are the same file. The running stand applies it the usual way.
In the field
The same stand, in a pocket
The Android app is not a second product. Sales, warehouse and managers talk to the same stand the office uses — same documents, same prices.
Same documents
Orders, stock and customers are the office modules. There is no second price engine and no second set of papers.
Three jobs, one app
Routes and orders for the representative, scans and counts for the warehouse, Field Desk for the manager.
Android, from the cabinet
The field app is Android. The installer is in the cabinet, next to the stand the person already has.
Your stand, not a shared demo
Talk to us about a stand. The docs show where to click; this page is what the subscription actually runs.