# Glossary > Short definitions of the terms used across the Coritan docs, from billing cycle and credit to floating IP and server. Source: https://www.coritan.com/docs/platform/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. ## Account and API Access token : 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](/docs/api/authentication/#access-and-refresh-tokens)). API key : A key you create on the **API keys** tab of **Settings**, with a label, permissions and allowed addresses. The Coritan API does not accept these keys yet ([Manage API keys](/docs/account/api-keys/)). Recovery code : 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](/docs/account/two-factor-authentication/)). Refresh token : The token that gets a new access token without your password. It lasts 30 days by default ([Authentication](/docs/api/authentication/#access-and-refresh-tokens)). Session : A browser or a script that is signed in to your account. Changing your password ends every session ([Sign out and end sessions](/docs/account/sessions/)). Two-factor authentication : Signing in with your password and a six-digit code from an authenticator app on your phone ([Turn on two-factor authentication](/docs/account/two-factor-authentication/)). ## Billing Add-on : 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](/docs/get-started/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](/docs/mail/billing/)). Auto-pay : 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](/docs/billing/payment-methods/#turn-auto-pay-on-or-off)). Automatic top-up : 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](/docs/billing/automatic-top-up/)). Billing cycle : 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](/docs/billing/change-plan/)). Billing mode : 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](/docs/billing/#prepaid-and-postpaid-accounts)). An organization has a billing mode of its own, which decides who takes its customers' payments ([How organizations work](/docs/organizations/how-organizations-work/#how-money-moves)). Cancellation : 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](/docs/billing/cancel-a-service/)). Credit balance : 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](/docs/billing/add-credit/)). Dispute : A payment you asked your bank to reverse ([Transactions and payment attempts](/docs/billing/transactions/)). Hourly billing : 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](/docs/billing/hourly-billing/)). Invoice : A bill in US dollars that Coritan raises for an order, a renewal or a plan upgrade ([Pay an invoice](/docs/billing/invoices/)). Monthly cap : The most an hourly service costs in a calendar month: 672 hours of its hourly price, by default. Once a service reaches it, Coritan stops charging it until the 1st of the next month ([How hourly billing works](/docs/billing/hourly-billing/#the-monthly-cap)). Payment attempt : One try at charging a card or a PayPal account ([Transactions and payment attempts](/docs/billing/transactions/)). Payment method : A card or PayPal account saved on your account. Coritan charges your default method for renewals and automatic top-ups ([Manage payment methods](/docs/billing/payment-methods/)). Plan : 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](/docs/billing/change-plan/)). Renewal : 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](/docs/billing/)). Suspension : 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](/docs/billing/failed-payments/)). Transaction : A record of money moving on your account: a payment, a refund, or credit added or used ([Transactions and payment attempts](/docs/billing/transactions/)). ## Services Location : The data centre a service runs in. When you order an instance or a server, you choose it in the **Location** section of the order page, where each location shows its airport code, such as `FRA` ([Data centres and locations](/docs/platform/data-centres/)). Service : One thing you pay for, such as an instance, a server, a floating IP or a mail service. The **Services** page lists every one ([Manage your services](/docs/get-started/services/)). Tag : 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](/docs/get-started/tags/)). ## Cloud Compute Backup : A full copy of an instance's disk, saved as a compressed archive. An instance can hold 16 backups ([Back up and restore an instance](/docs/cloud-compute/backups/)). Image : The operating system an instance starts from. The API calls an image a *template* ([Operating system images](/docs/cloud-compute/images/)). Instance : A Cloud Compute virtual machine, with its own disk, operating system, public IP address and console ([Cloud Compute](/docs/cloud-compute/)). Primary address : The IPv4 address that comes with an instance. More addresses are floating IPs that you attach ([Manage an instance's addresses and names](/docs/cloud-compute/networking/)). Rescue mode : 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](/docs/cloud-compute/rescue-mode/)). Snapshot : The state of an instance's disk at one moment, which you can roll the disk back to. An instance can hold 8 snapshots at a time ([Take and roll back instance snapshots](/docs/cloud-compute/snapshots/)). Traffic allowance : The amount of data an instance can transfer in a calendar month, set by its plan ([How instance traffic is counted](/docs/cloud-compute/traffic/)). ## Container Apps Free server : A server on the free plan. It sleeps when nobody is using it and starts again when a player joins or when you wake it ([How free servers work](/docs/managed-containers/free-servers/)). Primary port : The address and port that players join a server at. A server can have more ports for plugins and tools ([Manage server ports](/docs/managed-containers/ports/)). Server : A Container Apps container that runs a game server, a database or an application for you ([Container Apps](/docs/managed-containers/)). Shared address : 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](/docs/managed-containers/ports/)). Snapshot : A full archive of a server's files, kept in your account's snapshot storage. It stays after the server is deleted, and you can restore it onto any of your servers ([Snapshots](/docs/snapshots/)). Snapshot allowance : The most that all your server snapshots together may take up, including the snapshots of servers you have deleted ([How snapshot storage works](/docs/snapshots/storage-allowance/)). Subuser : 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](/docs/managed-containers/users/)). ## Networking Anycast : 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](/docs/platform/network/)). DDoS Shield : 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](/docs/ddos-shield/)). Floating IP : 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](/docs/floating-ips/)). Host : An address in a subnet that you can attach ([How subnets work](/docs/floating-ips/subnets/)). Join address : 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](/docs/proxies/join-addresses/)). Point of presence (PoP) : 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](/docs/platform/network/)). Pool : A set of floating IP addresses in one region. Every floating IP comes from a pool, and the **Pools** tab lists the pools that have addresses in stock ([IP pools and regions](/docs/floating-ips/pools/)). Protection profile : The DDoS Shield settings for a floating IP: how strictly it is filtered, its rate limits and its rules. Every address starts on the *platform default profile*, and you can give it a profile of its own ([Change a floating IP's DDoS protection](/docs/floating-ips/shield-settings/)). Reverse DNS : The hostname that a lookup of an address returns. Mail servers check it before they accept mail ([Set reverse DNS for a floating IP](/docs/floating-ips/reverse-dns/)). Subnet : A block of consecutive IPv4 addresses that you hold as one floating IP and attach one host at a time ([How subnets work](/docs/floating-ips/subnets/)). Web proxy : 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](/docs/proxies/web-proxies/)). ## Websites and DNS DNS zone : The records for a domain and every name under it ([How DNS hosting works](/docs/websites/dns/)). Load balancer : 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](/docs/websites/load-balancing/)). Nameservers : The servers that answer DNS queries for a domain. Coritan's are `ns1.coritan.com` to `ns8.coritan.com` ([How DNS hosting works](/docs/websites/dns/)). Proxied record : 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](/docs/websites/dns/#proxied-records)). Registration : Your right to a domain for the period you pay for, held through Coritan ([How domain registration works](/docs/websites/domains/)). TTL : How long, in seconds, resolvers may keep a DNS answer: from 60 seconds to 86,400 seconds ([How DNS hosting works](/docs/websites/dns/#ttl)). ## Mail Alias : 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](/docs/mail/mail-hosting/aliases/)). Mail Hosting : Mailboxes on your own domain, which people read in a mail app or in webmail ([How Mail Hosting works](/docs/mail/mail-hosting/)). Mailbox : 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](/docs/mail/mail-hosting/mailboxes/)). Send API key : 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](/docs/mail/smtp-relay/api-keys/)). Sending domain : A domain verified on an SMTP Relay service. The From address of every message must be on one ([How SMTP Relay works](/docs/mail/smtp-relay/)). SMTP credential : A username and password that an application uses to sign in to SMTP Relay ([Send over SMTP with credentials](/docs/mail/smtp-relay/credentials/)). SMTP Relay : Sends the mail your software writes, over SMTP or an HTTPS API, and reports what happened to each message ([How SMTP Relay works](/docs/mail/smtp-relay/)). Suppression list : 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](/docs/mail/smtp-relay/suppressions/)). ## Organizations Customer : Someone who buys from an organization. A customer account belongs to that organization only and is not a Coritan account ([How organizations work](/docs/organizations/how-organizations-work/)). Linked product : An organization's product that a Coritan product backs, such as a Container Apps plan, so that an order creates the real resource. A *standalone* product is one the organization delivers itself ([How organizations work](/docs/organizations/how-organizations-work/)). Mail tenant : 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](/docs/organizations/mail/)). Member : 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](/docs/organizations/how-organizations-work/)). Organization : A reseller brand you run on Coritan, with its own customers, products, prices, storefront, staff and payouts ([Organizations](/docs/organizations/)). Payout : What Coritan's payment gateways collected for an organization, less refunds, chargebacks and the *platform fee*, a percentage Coritan sets for each organization ([Track your payouts](/docs/organizations/billing/payouts/)). Staff console : Where an organization's team looks after its customers from day to day: their accounts, services, invoices and support conversations ([The staff console](/docs/organizations/staff-console/)). Step-up : 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](/docs/organizations/staff-console/sign-in/#confirm-it-is-you)). Storefront : The site where an organization's customers browse, order, pay and manage what they bought ([Build a storefront on the Organization API](/docs/organizations/storefront/)). Storefront account : 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](/docs/organizations/staff-console/team-and-settings/#change-a-member-s-storefront-account)). ## Support Conversation : 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](/docs/support/conversations/)).