Home › Running the fleet

Glossary

The words used in the fleet console, in plain language.

Tenant: One customer's own copy of OPSAVOR. Every restaurant company gets its own, completely separate from everyone else's, so one customer can never see another's information.
Demo tenant: A practice copy filled with made-up data, used for showing OPSAVOR to people or trying things out. It never holds real customer information.
Environment: What a tenant is for: production (real customers use it every day), staging (a rehearsal copy where new versions are tried first), testing or development (the team's own checks), or demo (made-up data).
Status: How a tenant is doing right now: running (working normally), creating or updating (changing, will finish by itself), suspended (paused on purpose), or failed (something went wrong and a person needs to look).
Platform, version, release: The platform is the OPSAVOR software a tenant runs. A release is a numbered version of it, such as platform-v0.8.1. Newer numbers are newer versions.
Image: The packaged copy of a particular version that is installed for a tenant. "Which version is it on?" is the same question as "which image does it run?".
Upgrade window: A weekly stretch of quiet hours, for example Tuesday to Thursday 2 to 5 in the morning, when it is OK to move real customers to a new version. Outside it, real customers are left alone.
Rollout: Putting a new version onto many tenants safely: practice and test copies first, then real customers a few at a time, checking each is healthy before moving on.
Wave, canary, soak: A wave is one batch of customers updated together. The canary is the very first small batch, an early test. Soak is the pause to watch for problems after a batch before the next one starts.
Roll back: Go back to the version before. Use it if a new version causes trouble.
Health check: A quick test that a tenant is switched on and answering.
Backup, restore: A backup is a saved copy of a customer's data at one moment. Each customer's copy takes one every day, before every update and before every restore; staff can take one any time. Restore puts the data back exactly as it was then, replacing what is there now; the customer's copy restarts to do it.
Business day: A restaurant's day as its point-of-sale counts it: from the time the day starts (often 4:00 or 4:01 AM) to the same time the next morning, so late-night sales belong to the night before. Each location sets its own, to the minute.
Suspend: Pause a customer on purpose, for example for a missed payment. Nobody can sign in, but their data is kept. Unsuspend brings it back.
Resize: Give a customer more or less computer power (small, medium, large). Bigger copes with more people and costs more.
Intake address: The email address a customer's suppliers send invoices and receipts to. Attachments are read automatically and appear for the owner to confirm. Regenerate (or Rotate, in the product) gives a new address and switches the old one off immediately.
Impersonate: Open a customer's account as that person, to help with a problem. You have to give a reason, it is recorded, and the link only works for 15 minutes.
Model (the AI reader): The AI that reads a customer's invoices and reports. Evaluate tests a model on sample documents so you can compare before switching.
Plugin: An add-on that turns a customer's own records into something useful: figures, a daily brief, reminders, a page of its own. It does nothing until the customer's owner approves what it asks for. The old Pulse, Brief and Alerts screens are no longer built in: they come back as plugins, such as Business Intelligence.
Store plugin: A plugin OPSAVOR publishes in the fleet console's store, signed, for staff to give to customers. Each lives in its own repository in the platform-plugins organization.
Plugin built here, local plugin: A plugin an owner made inside their own copy, often with Savy's Plugin Builder. It is limited (notices in the app only, no personal details, a small daily model budget) and waits for the owner's approval. The owner can Offer to OPSAVOR, which sends the plugin and never their records.
Dev tenant: A tenant where staff develop a plugin on real records. Every push to the plugin's repository runs it there, and the store approves its betas there. Stable versions still need the owner.
Beta channel: The track that gets vX.Y.Z-beta.N versions of a plugin. The stable channel gets only vX.Y.Z. A tenant can also be pinned to one exact version.
Grants: What a plugin asks to be allowed to do, such as which records it reads, whether it sees people, uses the AI model or sends notices. The owner sees them in plain words and approves. An upgrade that asks for more waits for approval.
Review (Mark reviewed): An owner or manager marks a row in a plugin's table or list as dealt with. It folds away and stops producing notices until the figures change. It needs a platform release that includes plugin reviews.
Data export: A copy of customers' documents and what was read from them, saved to storage for the data-science team. It never changes anything for a customer.
Audit: The permanent record of who did what and when. It cannot be edited.
Sign-in provider: Lets a restaurant's staff sign in with Google or Apple instead of a password.
Ingest, reading, confirm: An ingest is one document that came in. A reading is what OPSAVOR extracted from it. Nothing counts toward a customer's numbers until a person (or a trusted automatic check) confirms the reading.