Skip to content
Avaloi

Glossary

Plain definitions of the words you meet in the Avaloi dashboard, the API, and the help articles, in alphabetical order.

The words Avaloi uses in the dashboard, the API, and these articles. A term marked (planned) names a feature that is not built yet.

  • Add-on (planned): an extra you will be able to add to a plan. None exist until billing arrives.
  • API key: a named secret starting with hk_live_ or hk_test_, with scopes, an optional expiry, and an optional IP allowlist. Shown once.
  • Bot protection: the per-environment handling of automated traffic. Modes: Off, Monitor, Challenge suspicious, and Block definite bots.
  • Branch environment: any environment other than live, on its own Git branch with its own database and content store.
  • Build: the run that turns a commit into a release by running the avaloi.yml steps in a fresh container, for up to 20 minutes.
  • BYOD node (planned): a server you own, enrolled to run your sites. The enrollment flow exists today for Avaloi staff only.
  • Classic mode: the stored name of SFTP mode. Code is writable, so wp-admin can install plugins and themes. New staging and multidev environments do not start here: you switch to it.
  • Clone content: copying the database and uploads from one environment into a branch environment, with the hostname replaced. Code never moves this way.
  • Connection mode: Git mode (the default) or SFTP mode for staging and multidevs. Switch it with the SFTP | Git switch on the Code card on Info. Live is always in Git mode.
  • Company: your tenant. Members, sites, API keys, SSO, labels, and activity belong to it.
  • Content store: an environment's own copy of wp-content/uploads. Never in Git.
  • Cron job: a WP-CLI command Avaloi runs on a schedule, at most once every 5 minutes. The last run's output stays 7 days.
  • Edge cache: Cloudflare's cache in front of your server. Today it holds static files such as images, CSS, and JavaScript. Caching whole pages at the edge is not switched on yet.
  • Enrollment token: a single-use token, valid 15 minutes and shown once, that lets a new server join Avaloi.
  • Environment: a reachable copy of your site: a code branch, a database, a content store, and a temporary domain.
  • Force HTTPS: sends HTTP to HTTPS on every hostname, or sends every hostname to the primary domain.
  • Git mode: the default code mode, for live and for new staging and multidev environments. Code deploys from your repository as a read-only release.
  • Cloudflare DNS: hosting your domain's DNS records in a Cloudflare zone that Avaloi manages for you. Records are DNS-only.
  • Idempotency key: the Idempotency-Key header on every POST. Avaloi stores the first answer 24 hours and replays it for the same key and body.
  • IP deny: the per-environment list of blocked addresses and ranges, with allow entries that let an address through.
  • Job: one change to a server. It is queued, sent to the server, running, done, failed, or cancelled, and shows progress.
  • Job group: one bulk action across several environments, with one child job and one result per site.
  • Label: a colored tag that belongs to your company. Filter the Sites list by it and run bulk actions on it.
  • Live: the environment that serves your domains. It runs main.
  • Node: a server that runs sites. A Simulated node runs test sites at no cost.
  • Owner: the one member who can transfer ownership, manage SSO, and close the company.
  • Overage: usage past your plan's allowance for visits (or server bandwidth), CDN bandwidth, or disk. It never stops a site. It bills at $1 per 1,000 visits, $0.10 per GB of server or CDN bandwidth, and $2 per GB of disk, on your next invoice. See Billing and plans.
  • Premium staging: a staging or multidev environment on a smaller, slower server than live, with half of live's PHP threads and memory. Up to five per site, counted apart from the 10 standard staging and multidev environments.
  • Prepare first: adding only the TXT records for a domain, so the certificate issues before the CNAME moves. Moving the CNAME is the cutover.
  • Primary domain: the domain in the WordPress home and site URLs. Other domains send visitors to it.
  • Release: a read-only copy of your code built from one commit. Avaloi keeps the last 10.
  • Request ID: the identifier on every API response. Quote it when you write to support.
  • Restore: bringing back the database, the files, or both from a snapshot. Avaloi takes a snapshot first.
  • Role: what a member can do: Owner, Admin, Developer, Billing, or Viewer for the company; Site Admin or Site Developer for one site.
  • Rollback: activating an earlier release. It changes code only and needs no build.
  • Safe Updates (planned): plugin updates checked with visual comparisons. Not built.
  • Saved view: a set of Sites list filters you saved to apply again.
  • Scope: one permission on an API key, such as sites:read.
  • Server cache: the page cache on your site's server. It keeps pages for visitors who are not logged in for 10 minutes. Clear cache clears it and the edge cache together.
  • SFTP account: a login for moving files. Each environment has a primary SFTP and SSH user; extra accounts each see one folder.
  • Site: a WordPress install with its repository, environments, domains, and people.
  • Site preview: a view of the environment on its temporary domain for one hour to seven days, marked x-avaloi-preview: active.
  • Snapshot: a saved copy of an environment's database, content store, and settings. Manual, system, or daily.
  • Spend cap: the monthly amount that stops agents and API keys from buying, and stops Avaloi from billing overage once spending and overage together reach it. Sites keep running.
  • Staging: the environment created with every site, on the staging branch, as a copy of live.
  • Step-up: the extra confirmation before a sensitive action, such as typing your account password again to reveal a secret.
  • Temporary domain: the hostname every environment gets when it is created, one label under avaloi.com, such as elric.avaloi.com. You can rename it. See temporary domain.
  • Test site: a free site on a simulated server. It works in every tab and needs no plan.
  • Visits: the billing unit. One visit is one unique visitor in a day (one IP address and browser pair), with known bots excluded. Visits are counted for the whole account each month and shared by all your sites. They come from the server's access log, not from Cloudflare, unless the server's count for a day is missing.
  • Web root: the folder the site is served from. It can be a subfolder.
  • Webhook (planned): a message Avaloi will send to your URL when something happens. Not built.
  • Writable path: a folder that stays writable on a read-only release, such as uploads. PHP files there do not run.
  • Zero-touch attach: adding a domain whose DNS is on Cloudflare DNS. Avaloi writes every record itself.
  • Zone: one domain's set of DNS records on Cloudflare DNS.
  • Zone snapshot: a saved version of a zone, taken on every change, that you can roll back to.

Still stuck?

Email [email protected] with your site name and what you tried, or send us a message.