ZuloOne
English
CabinetAccount
Sign in
Menu

How the stand is hosted

Updated

You subscribe. ZuloOne runs the software. Your documents live in a database that no other company shares. Office work is in the browser. The warehouse and sales reps use the Android app — same company, same documents.

Note

Neighbours cannot see your invoices. A neighbour's busy day does not take yours down. This is not one big database with a company column.

The stand is its own process and its own database. People open it on your own address, over HTTPS. Scripts, compilation, and background jobs run inside that process. They never run against another company's database.

Hosting, upgrades, backups, and support are in the subscription. An upgrade takes a snapshot first and can go back. You can export data and configuration whenever you want.

When you change how the stand works, you do not edit Production by hand. You pack the change, try it on Test, two people sign it off, then it goes live. That desk is Lifecycle Portal, on the Business and Enterprise plans. A smaller plan still has the stand; the Test–Production cycle is on those two.

The same business files — JSON for the objects, C# for the scripts — are edited in the stand's web editor or in ZuloOne Studio for Visual Studio Code. A save is on the stand in a few seconds.

How to#

To use the stand you already have, open it at the address you were given.

To ship a change, open Lifecycle Portal (Business and Enterprise). Then:

  1. Open Lifecycle Portal — the left-menu map.
  2. Deploy a Test environment if you do not already have one.
  3. Ship a package — upload, install on Test, mark Ready, release to Production.
  4. Back up an environment before a risky change, if you want a restore point.
  5. Remove an old package only after it is installed nowhere.

The phone app is the same stand in a pocket — Install the phone app.

Example

Acme's people sign in at acme.zulo.one. Documents sit in Acme's database. A Test stand at acme-test.zulo.one is a copy with mail switched off. A .zulopkg is installed there first. Two people press Mark Ready for production. Then Release puts it on Production.

Tip

Lifecycle Portal's buttons are in English even when the office stand is in Ukrainian, Russian, or Arabic. The labels in these pages match the portal.

See also

Was this page helpful?