# Licences and editions

[Wiki](../README.md) / [Operations](README.md)

## Choose an edition

| Edition | Use | CPU allocation | Active user databases | Native backup and restore |
|---|---|---|---|---|
| Community (default) | Any use, including production and business use | Any number of allocated CPUs | Three, plus `system` | Not included |
| Commercial | Any use, with more databases and native backup and restore | Up to the licensed core count, per instance | Any number | Available with the backup/restore entitlement |
| Enterprise | Commercial plus [replicas on other instances](replicas.md#replicas-on-another-instance) and support | Up to the licensed core count, per instance | Any number | Available |

A fresh instance runs Community with no configuration: no key, registration
or online activation. Community is free for any use, including production and
business use. It includes Cypher, Bolt, GDS algorithms, APOC utilities, vector,
full-text and spatial indexes, TLS, users and roles, change streams,
subscriptions and same-instance replicas. An instance that other instances
replicate from needs an Enterprise licence (from version 1.6.5);
[contact us](/contact?topic=enterprise) for one.

Community permits **three active user databases plus `system`**, and a replica
counts as a database. `GDB_INITIAL_DATABASE` selects the home database, which
is always active. Other persisted user databases open in name order up to the
limit; the rest stay offline and untouched, and a restart with a different
selection switches between them. Creating a database beyond the limit returns
a licence restriction. Commercial supports any number of active user databases.

Commercial term totals per core, per instance, for one, two, three or five
years:

| Currency | 1 year | 2 years | 3 years | 5 years |
|---|---|---|---|---|
| USD | $400 | $740 | $1,000 | $1,500 |
| EUR | €370 | €685 | €925 | €1,390 |
| GBP | £320 | £590 | £800 | £1,200 |

Longer-term amounts cover the entire selected term. You choose the currency on
the pricing page or in your account before checkout; automatic renewals are
charged in the currency you bought in.

The current licence metric is allocated logical CPUs, rather than all physical
cores on a host. A fractional CPU quota rounds up: 1.5 allocated CPUs requires
two licensed cores. Set a container CPU limit that matches your purchased capacity.

## Perpetual licences

A perpetual Commercial licence is a single payment and never expires. It covers
one major version of Galactus DB: every release of that major, and of the
majors before it, on the licensed instance and core count. Writes never stop
and there is nothing to renew.

| Currency | First two cores | Each further core | Upgrade to a later major version |
|---|---|---|---|
| USD | $2,725 | $1,000 | $700 for the first two cores, $250 for each further core |
| EUR | €2,520 | €925 | €650 for the first two cores, €230 for each further core |
| GBP | £2,180 | £800 | £560 for the first two cores, £200 for each further core |

One 8-core instance is $8,725, paid once.

- **Version.** A perpetual key runs on Galactus DB 2.5.0 and later.
- **Updates.** Every release of the licensed major version is included.
- **A new major version within 12 months.** If the next major version is
  released within 12 months of your purchase, your licence covers it at no
  charge. Open the licence card, choose **Upgrade or add cores**, and check out
  to collect the new key.
- **Upgrading later.** After that, the upgrade price moves the licence to the
  current major version. It keeps covering the earlier ones, and a major
  version released within 12 months of a paid upgrade is included in turn.
- **More cores.** Add cores to a perpetual licence at the price of a further
  core: choose **Add cores** on its licence card.
- **From a term or evaluation licence.** Choose **Perpetual** as the term when
  you renew or upgrade a licence, and the same licence ID becomes perpetual.

Buy one from **Your account → License a commercial instance** by choosing
**Perpetual** in the term list. It is always a one-off payment. Install it
[like any Commercial key](#install-a-commercial-licence).

`CALL gdb.license()` shows a perpetual key with a null `expiry` and the versions
it covers, such as `up to 2.x`.

A server whose major version is newer than the key covers does not start, and
says so in its log. It stops before opening the data directory, so your data
stays in the format the licensed version reads. Run a release the key covers,
or install the upgraded key and start again.

## Free 30-day Commercial evaluation

Use an evaluation to test **multiple active user databases and native server
backup/restore** before buying. Cypher, GDS, APOC and indexes remain available
as usual.

- **Who qualifies:** a signed-in account with a verified email address that has
  never received an evaluation. Previous administrator-issued evaluations count.
- **Limit:** one evaluation per account, for one instance and its selected
  allocated CPU count. Expiry, reissue and upgrading do not reset this limit.
- **Duration:** exactly 30 days from generating the key, not from installing it.
  Self-service evaluations have no additional grace period.
- **Cost:** free. No payment details, subscription or automatic charge.
- **Use:** development and testing only, including evaluation within a business.
  Use a test instance rather than a business production database.

### Generate your key

1. Start a test instance using the [Docker quickstart](../getting-started/quickstart.md).
   It runs Community without a key.
2. In Explorer or your database client, run `CALL gdb.license();`. Copy the
   instance ID and allocated CPU count. Use the allocation reported by Galactus,
   not the total cores on the physical host.
3. Register on the Galactus DB website, verify your email, and sign in.
4. Open **Your account → Try Commercial free for 30 days**. Enter your licensee
   or organisation, instance ID and allocated CPU count. Check these before
   submitting: the key is bound to this instance and allocation.
5. Read and accept the evaluation conditions, then select **Generate evaluation
   key**. Your 30 days start immediately.
6. Select **Download licence** on the new evaluation card. The card shows the
   exact expiry date and time in UTC. Follow **Install a Commercial licence**
   below; evaluation keys use the same installation steps and `commercial` mode.

If your account already received an evaluation, the form is replaced with a
message. You can download the existing key again. **Reissue key** replaces its
token without changing the instance, CPU count or expiry. Contact support if
you entered the wrong details or need an administrator-reviewed extension.

### At expiry and when upgrading

At expiry, **writes and restore stop**. Reads and entitled native backup exports
remain available so you can retrieve your data. Removing the evaluation key
does **not** return that data directory to Community. To keep writing
to it, install a paid Commercial key.

To upgrade without moving your data:

1. On the evaluation card, select **Upgrade to paid Commercial**.
2. The purchase form fills in the existing licensee, instance ID, CPU count and
   licence ID. Keep those values unchanged and choose a paid term. This upgrade
   is a one-off purchase, with no automatic renewal. Contact support for a change
   in allocation or instance.
3. Complete checkout. Once payment is confirmed, download the replacement key
   from the same licence card. The paid term extends from the later of your
   evaluation term end or the payment date, with the paid licence's 14-day grace.
4. Replace the installed licence file and recreate the database container using
   the command below. Your existing database remains in place. The website does
   not install the replacement key automatically.
5. Run `CALL gdb.license();` again to confirm the status and new expiry.

Administrator-issued evaluations can have a different duration and grace period;
the dates on their licence cards are authoritative.

## Manage your licences

Sign in to **Your account** on the Galactus DB website. Your account lists your
licences, instance IDs, core counts and expiry dates. From there you can purchase,
download, renew or reissue a licence.

A licence identifies the product, licensee, instance, core count and expiry.
Use `CALL gdb.license()` to read the instance ID and CPU allocation from your
running database before purchasing. Keep that ID with the data directory; for
an instance you have not started yet, choose a stable `GDB_INSTANCE_ID` and use
it both in your purchase and your database configuration.
Renewals extend the licence term; reissues replace the key without extending its expiry.

## Install a Commercial licence

Download your licence and save it as `galactus.license` beside your Compose file.
Add a `compose.override.yaml` with the following settings, using the exact
instance ID and core count on your licence:

```yaml
services:
  db:
    cpus: 2
    environment:
      GDB_LICENSE_MODE: commercial
      GDB_INSTANCE_ID: your-instance-id
      GDB_LICENSE_FILE: /run/licenses/galactus.license
    volumes:
      - ./galactus.license:/run/licenses/galactus.license:ro
```

The licence file must be readable by the container's UID/GID 10001.
Alternatively, supply the licence token in `GDB_LICENSE`. If
`GDB_LICENSE_FILE` is set, the server reads that file.

Recreate the database container to load the settings:

```sh
docker compose up -d --force-recreate db
```

Check the active licence in Explorer or a driver:

```cypher
CALL gdb.license();
```

| Column | Meaning |
|---|---|
| `instance_id` | The instance ID a key must name |
| `num_cores` | The CPUs allocated to this instance |
| `core_metric` | How cores are counted: `allocated_vcpu` |
| `status` | `active`, or the reason writes are refused |
| `expiry` | When the installed key expires; null for a perpetual key and when no key is installed (from 2.5.0) |
| `versions` | The versions the installed key runs: `all` for a term key, `up to 2.x` for a perpetual one; null when no key is installed (from 2.5.0) |

## Renewal and expiry

Choose automatic renewal for a new 1-, 2- or 3-year subscription, or a one-off
purchase for any term. Five-year purchases require manual renewal. Existing
one-off licences are not automatically enrolled. **Manage billing** in your
account lets you update payment details or cancel future renewals; cancellation
does not shorten an already paid licence.

New Commercial licences include **14 days after the paid term** to install a
replacement key. The account displays the term end and signed expiry separately.
Automatic renewals keep the original billing schedule; grace never accumulates.
A failed payment grants no extension. Customer and administrator notifications
cover payment problems, cancellation, approaching expiry and missed renewal.
Older tokens retain their original signed expiry until replaced.

Install the renewed or reissued file and recreate the database container to load
it. The database does not fetch keys from your website account automatically.

When a Commercial licence expires, reads and exports remain available, including
native backup exports under the existing backup entitlement. Writes and restore
operations are refused.
Open write transactions cannot commit after expiry. Explorer displays the
licence error returned by the database. Explorer does not need a separate key;
licence enforcement happens on the database server.

An invalid key, wrong instance ID or CPU allocation beyond the licensed count
also blocks writes. Check the error and `CALL gdb.license()` before retrying.
Native backup exports are also blocked for invalid keys, wrong instance IDs and
over-allocation. Removing the key from a previously licensed data directory does
not reset it to Community. Keep the licence metadata with that directory.

Verification happens locally with the issuer keys built into the release image.
The server does not contact Stripe or the website to activate or renew a key.
Installing a newer issue prevents that data directory from accepting an older
issue; reissue does not remotely revoke copies already installed elsewhere.

## Refunds

Licence fees are non-refundable once your key has been supplied, which happens
as soon as your payment is confirmed. Community is free for any use and the
Commercial evaluation runs for 30 days, so you can try everything before you
buy.

At checkout you agree to the [Licence Terms](/legal/licence-terms) and ask for
your key to be supplied straight away. If you buy as a consumer, your 14-day
right to cancel ends when the key is in your account; the email that comes with
your licence confirms what you agreed to. Your statutory rights are not
affected.

If a payment is refunded or disputed, the licence it paid for is suspended in
your account: its key can no longer be downloaded, reissued, renewed or
changed. [Contact us](/contact) first if a charge looks wrong.

## Related articles

[Docker deployment](docker.md) · [Configuration](configuration.md) · [Backups](backups.md)
