LICENSING

How Galactus DB licensing works.

Commercial licences are prepaid for each instance you run, for a term or once for good. The Licence Terms set out the agreement in full.

Community, Commercial and Enterprise

A fresh instance runs Community, which is free for any use, including production and business use. There’s no account, activation or licence key. Community uses any number of CPU cores and runs three active user databases plus the system database; a replica counts as a database. Commercial adds any number of databases and native backup and restore. Enterprise adds replicas on other servers and support from the Galactus team.

Try Commercial for 30 days

Each verified account can generate one evaluation key for one instance and its chosen CPU allocation. Any previous evaluation issued by an administrator counts towards that limit. The key lets you try any number of active databases and native backup and restore for development and testing only. The 30 days start when you generate it. There’s no extra grace period, no payment details to enter and no automatic charge.

When the key expires, writes and restore stop, but reads and backup exports still work. Removing the key won’t return that data directory to Community. To keep writing, upgrade from the licence card in Your account, install the paid replacement key and restart. Reissuing a trial key doesn’t extend the trial.

Generate an evaluation key · Read the full instructions

Prepaid terms

Each core on each instance costs $400 for one year, $740 for two years, $1,000 for three years or $1,500 for five years. In euros that is €370, €685, €925 or €1,390, and in pounds £320, £590, £800 or £1,200. Those are totals for the whole term, charged in the currency you choose at checkout. Taxes are added at checkout where they apply.

Perpetual licences

A perpetual licence is a single payment and never expires. It costs $2,725 (€2,520 or £2,180) for the first two cores on an instance, and $1,000 (€925 or £800) for each further core. It covers every release of the major version that is current when you buy it, and of the ones before it.

If a new major version is released within 12 months of your purchase, your licence covers it too: collect the new key from your account. Later on, an upgrade to the current major version costs $700 (€650 or £560) for the first two cores and $250 (€230 or £200) for each further core. You can add cores at any time at the price of a further core. A perpetual key runs on Galactus DB 2.5.0 and later.

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 first. If you buy as a consumer, you ask at checkout for your key to be supplied straight away, and your 14-day right to cancel ends when it is. Your statutory rights are not affected. The Licence Terms have the full detail.

What’s in your licence key?

Your signed, encrypted key records the product, edition, licensee, instance ID, core count and how cores are counted. It also includes issue and licence versions, the issue date and expiry. A perpetual key records the major version it covers. Keep your instance ID the same across restarts so the key continues to match.

Renewing your licence

You can choose automatic renewal for a new one-, two- or three-year subscription. Five-year terms renew manually. Paid licences give you 14 days after the term ends to install a replacement key. Self-service evaluations have no extra grace period. Grace periods don’t change your billing dates or carry over. Community allows three active user databases plus the system database. Commercial has no database limit.

When a licence expires

Writes stop, including commits from open write transactions. Reads and Commercial backup exports still work. Renew through your account, install the new key and restart the server to resume writing.

How we count cores

We count the logical CPUs allocated to each instance, including VM and container vCPUs, and round fractional allocations up. Set your container’s CPU limit to match the licensed count. Cores on the host that aren’t allocated to that instance don’t count.

Keys are checked locally

The server checks your key locally. Reissuing a key won’t remotely invalidate an older copy. Get in touch if you need to transfer a licence, change your core allocation or discuss your deployment.

Install or renew a licence

Manage licences