Glossary

Each term has a short definition and a link to the page that covers it. The terms are grouped by the part of Coritan they belong to, in alphabetical order within each group. The Learn pages explain the main ideas in more depth.

What a script sends in the Authorization: Bearer header of each Client API request. You get one by signing in through the API, and it lasts 30 minutes by default (Authentication).

A way for your own programs to work with Coritan without the dashboard, by sending requests over HTTPS and reading the answers (API).

A key you create on the API keys tab of Settings, with a label, permissions and allowed addresses. A script sends it as Authorization: Bearer ct_... to call the Coritan API as you (Manage API keys).

One of the ten codes you save when you turn on two-factor authentication. Each one signs you in once without your phone (Turn on two-factor authentication).

The token that gets a new access token without your password. It lasts 30 days by default (Authentication).

A browser or a script that is signed in to your account. Changing your password ends every session (Sign out and end sessions).

Signing in with your password and a six-digit code from an authenticator app on your phone. Someone who learns your password still cannot sign in without the code (Turn on two-factor authentication).

The plan for your whole account: Free, Pro, Business or Enterprise. It sets how many websites, load balancers and team members the account can have, and which website features and automatic backups come with it. It includes a Mail Hosting and an SMTP Relay service at no charge, and sets how much Object Storage the account uses free each month. Account plans are opening to accounts in stages, and every account starts on Free (How account plans work).

Another product you order with a service under Add-ons on its order page, such as a floating IP with an instance or Snapshot Storage with a server. Each add-on becomes a service of its own, and its first period is on the service's first invoice (Order a service). A dedicated sending address for SMTP Relay is ordered on a page of its own and billed as a service of its own (How Mail Hosting and SMTP Relay are billed). To raise a limit of a service you have, such as its number of ports, add a capacity add-on.

The setting that lets Coritan charge your saved payment methods for renewals. It is on for new accounts, and turning it off does not stop those charges yet (Manage payment methods).

Coritan charges your default payment method a fixed amount when your credit balance falls below a threshold you choose. It is off for new accounts (Turn on automatic top-up).

How often a service is billed. The API names the cycles hourly, daily, weekly, monthly, quarterly, semi_annually, annually and biennially, and one_time marks something you pay for once. You choose a cycle when you order (Change a service's plan).

Whether your account pays for a service before Coritan sets it up (prepaid, the mode every account starts in) or at the end of each billing cycle (postpaid) (Billing). An organization has a billing mode of its own, which decides who takes its customers' payments (How organizations work).

Ending a service, at the end of its term or at once. When the service ends, Coritan deletes it and its data (Cancel a service).

An add-on that raises one limit of a service, such as the number of ports on a server or of mailboxes on the Mail Hosting your account plan includes. It renews with the service, on the same date and billing cycle, and you can remove it at any time (Add capacity to a service).

Money on your account, held in US dollars, that pays invoices and hourly charges before Coritan charges a payment method. It never expires (Add credit to your balance).

A payment you asked your bank to reverse (Transactions and payment attempts).

Paying for a service by the hour from your credit balance, up to a monthly cap. A prepaid account can order hourly plans once it has added $10.00 of credit in total, by default (How hourly billing works). A service billed by use is charged for what it uses each hour instead, with no cap (Usage billing).

The use that every month includes at no charge for services billed by use. Every account has the web amounts for its web services, hybrid sites and static sites. An account with Server access has the server amounts for its instances, game servers and databases. They start again on the 1st (UTC) (Usage rates).

A Mail Hosting or SMTP Relay service that your account plan includes at no charge. You set each one up once, and Coritan resizes it when your plan changes (Set up the services your plan includes). For Object Storage, the plan gives free amounts each month instead (Free each month).

A bill in US dollars that Coritan raises for an order, a renewal or a plan upgrade (Pay an invoice).

The most an hourly service costs in a calendar month: 672 hours of its hourly price, by default. Coritan stops charging a service when the next hour would reach it, until the 1st of the next month (How hourly billing works).

What an account needs to order a Cloud Compute instance, a game server or a database, which are billed by use. Pro, Business and Enterprise include it, and a Free account adds it as an account add-on, in the same order as its first server. It includes data out only. A web deployment needs no plan (How usage billing works).

One try at charging a card or a PayPal account (Transactions and payment attempts).

A card or PayPal account saved on your account. Coritan charges your default method for renewals and automatic top-ups (Manage payment methods).

A service's price and how often you pay it. A product has one plan for each billing cycle it sells, such as RX-2 (Monthly) and RX-2 (Annually) (Change a service's plan). Your whole account also has an account plan.

The start of a service's next billing cycle. Coritan raises the renewal invoice up to 3 days before the renewal date, by default, and takes it from your credit first (Billing).

Coritan pausing a service, usually because an invoice is unpaid. With the default settings, a service is suspended a day after its invoice's due date and deleted later if the invoice stays unpaid (Failed payments and suspended services).

A record of money moving on your account: a payment, a refund, or credit added or used (Transactions and payment attempts).

Paying for what a service uses, measured by the second, with some use free each month. A web deployment, a Cloud Compute instance, a game server and a database ordered on your own account are billed this way, and have no price of their own (How usage billing works).

The data centre a service runs in. When you order an instance or a server, you choose it under Data centres on the order page, where each location shows its airport code, such as FRA. A deployment can run in several (Data centres and locations, Choose locations and scaling).

One thing you pay for, such as an instance, a server, a floating IP or a mail service. The Subscriptions tab of Billing lists every one (Manage your subscriptions).

A label of your own, such as production, that you put on a service, an instance or a server to find it again. Tags change no setting and cost nothing (Tag your services).

What your account plan includes for a deployment on older terms: build minutes, bandwidth and edge requests each calendar month, and room for your static sites' files. All the deployments you pay for share it. Past it, a deployment stops using more unless you allow overage, and a bigger plan or a pack raises it (How App Deployment is billed). A deployment billed by use has included amounts instead.

The Apps API's word for a deployment that is built from a git repository or run from a container image, which the dashboard calls a web service. Scripts written for Apps keep using it (Apps API).

What coritan.com called its product for apps built from git or run from an image, before App Deployment. Each app is a web service now, and the Apps API still answers (Container Apps and Apps in App Deployment).

A program packed with everything it needs to run, in a space of its own on a shared machine, with its own files and a set share of memory, processor time and disk. Each instance of a deployment runs in one (App Deployment, Cloud servers).

What coritan.com called its product for game servers, databases and other software from the catalogue, before App Deployment. Each Container Apps server is a deployment now, and keeps its address, its plan and its data (Container Apps and Apps in App Deployment).

The action that builds the branch, tag or commit you name and starts a release from it. Once the new release is healthy, it replaces the live release. A deployment that runs a container image reads Deploy an image instead, and you type an image (The three ways to start a release).

One thing you run on App Deployment: a game server or a database from the catalogue, a web service built from a git repository or run from a container image, or a static site. It has its source, its locations and its addresses, and each version of it is a release. In the Apps API, a deployment object is a release (App Deployment).

A set of variables that several deployments of your account, or of one organization, read, such as the address of a shared database. A deployment's own variables win over its groups' (Environments and variables).

Which releases a deployment's variable is for: production, preview, development (what you run on your own computer) or all of them (Environments and variables).

A game server on the free plan, which an organization can sell on its own storefront. coritan.com sells no free server. A free server sleeps when nobody is using it and starts again when a player joins (How free servers work).

A static site with server routes. The edge serves the files its build wrote, and sends every other request to its instances, which are billed like any other (Host a static site or a hybrid site).

One running copy of a release in one location, in a container of its own. A deployment runs one instance in each of its locations unless you set more, and a game server or a database runs one server in each location it was ordered in. On Cloud Compute, an instance is a virtual machine instead (Choose locations and scaling).

The release that serves production. Its status reads Live. A new release replaces it once the new release is healthy, and until then the live release keeps serving. The API names it current_release, and marks it with is_current (Deploy, promote and roll back releases).

Committing to a number of instances of a deployment and paying for them each month at the instance size's monthly price, whether they run all month or not. It is an older term: a deployment ordered on your own account is billed by use. Instances above that number are billed as pay as you go is (How App Deployment is billed).

Use past an allowance, billed for each unit from your credit or on your next invoice, up to your spend limits. It is off until you allow it on a deployment's Billing tab (How App Deployment is billed).

Paying for the seconds a deployment's instances run, at the instance size's hourly price, charged each hour from your prepaid credit. It is an older term: a deployment ordered on your own account is billed by use. The order charges the first hour, a stopped or sleeping instance costs nothing, and there is no monthly cap. An account billed by invoice pays monthly per location instead (How App Deployment is billed).

A release built from a branch other than the production branch, or from a pull request, at addresses of its own. It never replaces production, and you can promote a ready preview to production without building it again (Deploy from a git repository).

One of the two addresses a preview answers at, under the platform's domain for deployments: one for its branch, which follows the branch's newest ready preview, and one for its commit. The dashboard also calls them aliases (Deploy from a git repository).

The address and port that players join a server at. A server can have more ports for plugins and tools (Manage server ports).

The action that builds the newest commit on the deployment's production branch again, then replaces the live release once the new release is healthy. Use it after a build setting or a build-time variable changes, such as one whose name starts with NEXT_PUBLIC_. A deployment that runs a container image reads Pull again: it pulls the saved image again, with any new push under its tag. On Cloud Compute, rebuilding an instance is another action: it reinstalls the operating system (The three ways to start a release).

The action that runs the live release again with the variables, size and locations saved now. Nothing is built or pulled. Use it after a variable that only the running app reads, or the instance size, changes (The three ways to start a release).

One version of a deployment: a build of one commit, a container image, or a static site's files. The release that serves production is the live release. You start a release with Deploy a branch, Rebuild or Redeploy, and you can promote a preview or roll back to an earlier release. In the Apps API, a deployment object is a release (Deploy, promote and roll back releases).

The Apps API's word for an instance of an app. An app's instances keep nothing on their disks from one release to the next, so an app keeps its data in a database or in Object Storage (Apps API).

A project's code and its history, kept with git on a host such as GitHub. A deployment from git builds each release from one commit of a branch (Deploy from a git repository).

A new release that runs an earlier release's build output or image again, without building. You start one with Roll back to this… on a release that went live once (Roll back).

Software from the catalogue, such as a game server or a database, that Coritan installs and runs for you in a container of its own, with its own files, console and ports. It is a deployment, and one ordered in several locations runs a server in each, each with its own data. In these docs a server runs on App Deployment, and a Cloud Compute instance is a virtual machine (App Deployment).

The address of the machine a server runs on. Every server on that machine uses it, each on ports of its own (Manage server ports).

The API's name for a budget: a monthly amount for one deployment, or for all your services together, Cloud Compute instances included. The dashboard calls it a Budget, or a Monthly budget when you order a deployment. We email you as the month nears it. At it, the budget holds back previews, extra instances and new builds (and overage, on older terms) while production keeps serving, or stops every instance, as you chose. A game server or a database it stopped cannot be started again until the budget lets go (How App Deployment is billed).

A deployment whose build writes plain files, such as HTML, CSS and JavaScript, which the edge serves from every location with no instance. It costs nothing to run (only its builds and logs can be billed), and one ordered on your own account is not one of your account plan's websites (Host a static site or a hybrid site).

Another Coritan account that you give access to one of your servers, with the permissions you choose. Billing stays with you (Share a server with other users).

A deployment of your own code, built from a git repository at each push or run from a container image you built, such as a website or an API. It runs as instances of its live release, which can scale with traffic and sleep when idle. The Apps API calls it an app (Deploy from a git repository).

A share of a physical machine in a data centre that you rent, with its own processors, memory and disk. On a Cloud Compute instance you look after everything inside it, and on App Deployment Coritan installs the software and keeps it running (Cloud servers).

The operating system an instance starts from, such as Ubuntu or Debian. The API calls an image a template (Operating system images).

A Cloud Compute virtual machine, with its own disk, operating system, public IP address and console. You get full root access and install what you like on it (Cloud Compute). On App Deployment, an instance is a running copy of a release instead.

The IPv4 address that comes with an instance. More addresses are floating IPs that you attach (Manage an instance's addresses and names).

Starting an instance from a rescue image instead of from its own disk, so you can mount the disk and repair it (Repair an instance in rescue mode).

A pair of keys that signs you in to an instance over SSH, an encrypted connection for typing commands on it, without a password. You keep the private key on your computer and give the instance the public key, on its order page or its Access tab (Manage an instance's password and SSH keys).

The amount of data an instance can transfer in a calendar month, set by its plan (How instance traffic is counted). An instance billed by use also pays for the data it sends past the amount included each month (How Cloud Compute is billed).

A computer that runs as software on a larger physical machine, with its own share of processors, memory and disk and its own operating system. A Cloud Compute instance is a virtual machine (Cloud servers).

A copy of your data, kept so that you can get it back after a mistake or a failure. On Cloud Compute, a backup is a full copy of an instance's disk, saved as a compressed archive, and an instance can hold 16 (Back up and restore an instance). On App Deployment, snapshots have replaced backups, and a server keeps only the backups it already had (Manage server backups).

A copy of a disk, or of a server's files, at one moment, which you can go back to. An instance's snapshots stay with the instance, 8 at a time (Take and roll back instance snapshots). Coritan keeps a server's snapshots in your account's snapshot storage. They stay after you delete the server, and you can restore one onto another of your servers (Snapshots).

The most that all your server snapshots together may take up, including the snapshots of servers you have deleted (How snapshot storage works).

More room for server snapshots, which you order as a service of its own. It raises your snapshot allowance (Order more snapshot storage).

The pair of values an S3 tool signs its requests to Object Storage with: an access key ID and a secret key. Each key is read-only or read-write, and works on one bucket or on every bucket on your account (Create and revoke access keys).

A named container for files in Object Storage. A service holds up to 25 buckets, each in one region, and every bucket is private (Create and delete buckets).

Object Storage requests that write or list, such as an upload, one part of a large upload or a list of a bucket's objects. Each month your account makes some at no charge, and we bill the rest by the million (Which requests count).

Object Storage requests that read, such as a download or a HEAD request for an object. They cost less than Class A operations. Each month your account makes some at no charge, and we bill the rest by the million (Which requests count).

Data sent out to the internet. For Object Storage, it is what your buckets send out, such as the files people download, and it is free (Egress).

The address a tool connects to. Each Object Storage region has its own, such as https://s3.fra.coritan.com:7337 for Frankfurt. A region that also answers on port 443 shows its endpoint with no port (Connect an S3 client).

How Object Storage measures storage over time: one GB kept for a whole calendar month, where a GB is 1024³ bytes. 60 GB kept for half of a month is 30 GB-months (What a GB-month is).

One file in a bucket, stored under its full name, called its key, such as photos/2026/beach.jpg (Upload, download and delete objects).

Coritan's storage for whole files, kept as objects in buckets that your tools reach over the internet with the S3 API. You upload, download or delete one whole object at a time, where programs change files on a disk in place (Object storage compared with a disk, Object Storage). It is pay as you go: storage by the GB-month, requests as Class A and Class B operations, and no charge for egress (How Object Storage is billed).

The way most storage tools and code libraries talk to object storage, named after Amazon S3, which made it standard. Object Storage speaks it, so tools such as rclone and the AWS CLI work with it (Connect an S3 client).

Announcing the same address range from more than one point of presence, so that traffic enters the network close to where it was sent from (How the Coritan network works).

A record that DDoS Shield dropped traffic to one of your floating IPs at a high rate: which address, why, how large the attack was and how long it lasted. The Events tab of DDoS Shield lists them, and Coritan emails you when an attack starts and when it ends (Read attack events, DDoS attacks and protection).

Distributed denial of service: a flood of traffic sent from many machines at once to overload a server or its connection, so that real visitors or players cannot reach it (DDoS attacks and protection).

The filtering Coritan applies to the traffic to every floating IP on your account, at the point of presence where the traffic arrives (DDoS Shield).

A public IPv4 address, or a block of them, that belongs to your account instead of to one machine. You attach it to an instance or a server, and you can move it to another one later (Floating IPs).

An address in a subnet that you can attach (How subnets work).

The number that identifies a machine on the internet. An IPv4 address looks like 203.0.113.10, and an IPv6 address like 2001:db8::10. DNS turns names into these numbers (IP addresses, ports and reverse DNS).

A hostname, such as survival-smp.coritan.gg, that players type in their game to reach your server. The dashboard also calls it a game proxy (How join addresses work).

A Coritan site where our routers connect to the internet. Traffic to a floating IP enters the network there, and DDoS Shield filters it (How the Coritan network works).

A set of floating IP addresses in one region. Every floating IP comes from a pool, and the order page's Region section shows the pools, with the ones that have addresses of the size you chose in stock (IP pools and regions).

A number from 1 to 65535 that picks one service at an address, so that one machine can run many. Websites use ports 80 and 443, and a Minecraft server uses 25565 unless you change it. Each server on App Deployment has ports of its own (Manage server ports).

The DDoS Shield settings for a floating IP: how strictly it is filtered, its rate limits and its rules. Every address starts on standard protection, and you can give it a profile of its own (Change a floating IP's DDoS protection).

The hostname that a lookup of an address returns, set with a PTR record. Mail servers check it before they accept mail (Set reverse DNS for a floating IP).

A block of consecutive IPv4 addresses that you hold as one floating IP and attach one host at a time (How subnets work).

Copies of a website's files that Coritan's network keeps, such as pictures, fonts, sound and video files, and versioned scripts and stylesheets, so it answers visitors without asking the origin each time (Speed up a website with the cache).

A file that proves a site is the name in the address bar, such as www.example.com, so that browsers connect over HTTPS without a warning. Coritan gets certificates from public certificate authorities, does not charge for them, and renews them before they expire (How SSL/TLS certificates work).

A web proxy setting that, for the time you choose, shows the origin's address and the exact connection failure on Coritan's error pages, so you can debug a site that does not answer (Manage a website's origin).

The Domain Name System, the internet's directory. It turns a name such as example.com into the addresses and settings that computers need, such as the address of the server that runs your site (How DNS hosting works, Domains and DNS).

One entry in a DNS zone: a name, a type, a value and a TTL. An A record points a name at an IPv4 address, a CNAME record points it at another name, and an MX record names the servers that take a domain's mail (DNS record types).

The records for a domain and every name under it (How DNS hosting works).

Signatures on a zone's answers, which let resolvers check that the answers came from the zone's nameservers unchanged. Coritan signs every zone it hosts until you switch signing off, and resolvers check the signatures once you add the zone's DS records at the domain's registrar (Set up DNSSEC).

A name such as example.com that people type to reach your website or to send you mail. You hold it for as long as you pay for its registration (How domain registration works).

Coritan's servers at its points of presence that answer for your web proxies and proxied records. They serve HTTPS, run the WAF and forward each request to your origin (How web proxies work).

How Coritan's network connects to a website's origin. Flexible encrypts only the visitor's side, Full encrypts both sides without checking the origin's certificate, and Full (strict) encrypts both and checks it (Choose an encryption mode).

A full name, such as www.example.com or survival-smp.coritan.gg, that DNS turns into an address (Domains and DNS).

A setting that stops other websites showing a site's pictures on their own pages, which uses the site's bandwidth (Protect a website).

HTTP Strict Transport Security: a header that tells browsers to open a site only over HTTPS, for the time the site chooses (Choose an encryption mode).

Answers A and AAAA queries for one hostname with the address of one of your servers. It picks the server from its origin pools and skips servers that fail their health checks (How DNS load balancing works).

A server that answers DNS questions for a domain. The domain's registrar tells the internet which nameservers to ask. Coritan's are ns1.coritan.com to ns8.coritan.com (Change a domain's nameservers).

The server that runs your site or app behind a web proxy: a server on App Deployment, a Cloud Compute instance or a server somewhere else. The web proxy forwards each visitor's request to it (How web proxies work).

An A or AAAA record that Coritan answers with the addresses of its edge, so that visitors' requests pass through the edge and its WAF (How DNS hosting works).

A server that takes requests in place of another and passes them on. A web proxy does this for a website, and a join address does it for a game server (Web proxies, origins and the WAF).

A rule that sends a visitor who opens one address to another, such as an old page to its new place (Redirect visitors and set headers).

The company you register a domain through, where you renew it and set its nameservers. For a domain you registered on Coritan, you do both in the dashboard (Change a domain's nameservers).

Your right to a domain for the period you pay for, held through Coritan (How domain registration works).

The organization that runs a domain ending, such as .com. It keeps the list of every domain under that ending and the nameservers of each one, which you choose at the domain's registrar (Domains and DNS).

The DNS server that your device or network asks to look up a name, usually run by your internet provider. It asks the domain's nameservers and keeps the answer for as long as its TTL allows (Domains and DNS).

A line of information that comes with each answer to a visitor's browser, such as whether another site may show the page in a frame. A request header goes the other way, to the origin (Redirect visitors and set headers).

The encryption that protects a connection, which a browser shows with https:// at the start of the address. TLS is its current name and SSL the older one, and people use both. A site needs a certificate to use it (How SSL/TLS certificates work).

A name under your domain, such as www.example.com or shop.example.com. You create one by adding a DNS record for it in the domain's zone (Add, edit and delete DNS records).

How long, in seconds, resolvers may keep a DNS answer: from 60 seconds to 86,400 seconds. After you change a record, some visitors can get the old answer until its TTL runs out (How DNS hosting works).

A setting that asks every visitor a simple math question before a page opens, to keep automated traffic off a site under attack (Protect a website).

A web application firewall: it checks each request to a website on Coritan's network, and refuses the ones that look like attacks before they reach your origin. You turn it on or off for each web proxy (Protect a website, Web proxies, origins and the WAF).

A hostname, such as www.example.com, that Coritan's edge answers for. The edge serves the name over HTTP and HTTPS, checks requests with the web application firewall (WAF) and forwards them to your origin, the server that runs the site. The dashboard also calls a web proxy a route (How web proxies work).

An address with no storage of its own that delivers its mail to mailboxes on the same service. A catch-all takes the mail for every address on a domain that has no mailbox or alias (Forward addresses with aliases).

A signature that the sending server adds to each message, which receiving servers check against a key published in your domain's DNS. It proves that the message came from your domain and was not changed on the way. Coritan gives each domain two keys and replaces them every 90 days. A store's marketing email needs DKIM, SPF and DMARC records on its sending domain before it can send (Mail DNS records, Set up your sending domain and warm-up, How email reaches an inbox).

A TXT record that tells receiving servers what to do with a message that claims to come from your domain but fails SPF and DKIM: deliver it, treat it as suspicious or refuse it. Coritan starts each domain at p=none and moves it up as its real mail passes (How the DMARC stage ramp works, How email reaches an inbox).

How a mail app reads a mailbox. The mail stays on the server, so every app you sign in to shows the same messages and folders. Mail Hosting answers IMAP on port 993 with SSL/TLS (Connect a mail app to Mail Hosting, How email reaches an inbox).

A newer way for mail apps to read and send mail. Most mail apps use IMAP and SMTP instead (Connect a mail app to Mail Hosting).

Mailboxes on your own domain, which people read in a mail app or in webmail (How Mail Hosting works).

An address with its own storage, such as alex@example.com, that people sign in to with webmail or a mail app (Create and manage mailboxes).

The DNS record that tells other mail servers where to deliver mail for a domain. For Mail Hosting to receive a domain's mail, the domain's MX records must name its mail servers (Mail DNS records, How email reaches an inbox).

A key that lets an application send mail through one SMTP Relay service over HTTPS. It can only send (Create and revoke send API keys).

A domain verified on an SMTP Relay service. The From address of every message must be on one (How SMTP Relay works). A store's email marketing has a sending domain of its own, usually news. in front of the store's domain, which keeps marketing email apart from the sender that carries order emails (Set up your sending domain and warm-up).

How mail is sent: from a mail app or an application to a mail server, and from one mail server to the next. Mail Hosting and SMTP Relay take mail on port 587 with STARTTLS, or port 465 with SSL/TLS (Connect a mail app to Mail Hosting, Send over SMTP with credentials, How email reaches an inbox).

A username and password that an application uses to sign in to SMTP Relay (Send over SMTP with credentials).

Sends the mail your software writes, over SMTP or an HTTPS API, and reports what happened to each message (How SMTP Relay works).

A TXT record that lists the servers allowed to send mail for your domain, so that receiving servers can spot forged mail. A name has one SPF record, so you add Coritan's include: to the one you have. The same holds for a store's marketing sending domain (Mail DNS records, Set up your sending domain and warm-up, How email reaches an inbox).

The addresses an SMTP Relay service no longer sends to: those that bounced, complained or unsubscribed, and any you add yourself (Manage the suppression list).

Reading and sending mail in a browser, with no mail app to set up. Coritan's webmail is at https://www.coritan.com/webmail (How webmail works).

A campaign setting that sends two or three versions of an email to a small, random part of the audience, then sends the version with the best result to everyone else after a wait you set. Opens by mail privacy tools are left out of the count (Test two subjects against each other).

After at least 200 emails of a campaign are delivered, the campaign pauses itself if its bounce rate or its spam report rate goes over the limits you set. If two campaigns in a row pause, all marketing email pauses (Automatic pausing).

The words a person agreed to, when and how. A contact is subscribed only after it agreed, and the record stays after it unsubscribes (Consent and double opt-in).

A way of joining a list in which the person gets an email with a link and joins only when they click it. It proves the address is theirs (Consent and double opt-in).

A trial import that reads everything and counts what would happen, without adding or changing a single contact (Import contacts).

A figure from 0 to 100 for how often a contact opens and clicks the emails it gets. A click is worth more than an open, both fade over 90 days, and opens by mail privacy tools do not count (Open a contact).

Opens made by a mail privacy tool or a security scanner, which load every image as a message arrives. They say nothing about the reader, so reports count them apart and leave them out of open rates, clicks and engagement (Machine opens).

A placeholder such as {{ first_name }} that an email fills in with each reader's own details when it is sent. A fallback such as {{ first_name|default("there") }} covers a reader with no value (Merge tags).

A saved set of rules that picks contacts. Its people change as contacts change, so a campaign sent tomorrow uses tomorrow's matches (Segments).

A hint from 0 (clean) to 10, worked out from a campaign's subject and the words of its email. Mail filters make their own call, so a low score is no promise (Check before sending).

The first days of a new sending domain, when its daily limit starts at 50 emails and rises each day the sending stays clean. Mail apps are careful with a domain that has no history (Warm-up and the daily limit).

A password WordPress makes for one app, under Users > Profile > Application Passwords in WordPress. A store's WordPress import uses one to list the files attached to unpublished pages; revoke it there once the import ends (Store media).

How Coritan charges an organization for compute: Plans, the wholesale price of each plan its customers pay for, or Usage, the wholesale rate for what their servers use. A new organization starts on Usage, and a switch takes effect on the 1st of the next month (See what your customers' use costs you).

A store order that is paid and has shipped, or has been delivered when the store waits for delivery. An order with nothing to ship is completed once it is paid (Fulfil, refund and cancel store orders).

Someone who buys from an organization. A customer account belongs to that organization only and is not a Coritan account (How organizations work).

A platform product, as the guides also call it: an organization's product linked to a Coritan product (Platform product).

A Mail Hosting or SMTP Relay service that a customer ordered from an organization, with its own domains, mailboxes, credentials and sending reputation (Run Mail Hosting for your customers).

A Coritan account added to an organization with a role. The owner is the account that created the organization, and has every permission (How organizations work).

A reseller brand you run on Coritan, with its own customers, products, prices, storefront, staff and payouts (Organizations).

A pause on new orders for an organization, because its monthly usage budget is reached or an invoice for usage is unpaid past its reminders. Servers that already run keep running (See what your customers' use costs you).

What Coritan's payment gateways collected for an organization, less the platform cut on all its money, the wholesale price of the hosting it resold and its usage at wholesale (Track your payouts).

Coritan's share of the money an organization's customers actually pay it, store and hosting alike. The share is the tier of the calendar month's whole volume and applies to all of it; Coritan's own organizations pay none (The reseller program's terms).

An organization's product that a Coritan product backs, such as a server plan of App Deployment, so that an order creates the real resource. A standalone product is one the organization delivers itself (How organizations work).

Where an organization's team looks after its customers from day to day: their accounts, services, invoices and support conversations (The staff console).

A code from your authenticator, or your password, that the staff console asks for again before some actions. It lasts 10 minutes (Sign in to the staff console).

The site where an organization's customers browse, order, pay and manage what they bought (Build a storefront on the Organization API).

The customer account on an organization's storefront that the staff console signs a member in to, so that they can use the product as customers do (Manage the staff team and console settings).

A store checkout whose payment failed, or that the shopper did not pay within the time the store allows, 60 minutes unless it sets another. It has no order until the shopper pays (Follow up unpaid checkouts).

What an organization pays Coritan for the compute its customers' servers use: memory, CPU, disk and data out, each at Coritan's list rate less the wholesale discount, charged as the server runs (See what your customers' use costs you).

What an organization pays Coritan for the hosting it resells: Coritan's list price less the wholesale discount. The organization's own price for that hosting can be no lower than what it costs the organization. Compute on usage billing is charged by use instead (The reseller program's terms).

A support thread between you and the Coritan team, with a number such as #1042. You start one on the dashboard's Support page, and the dashboard also calls it a ticket, as in Open a ticket (Contact support from the dashboard).