Perpetual or Subscription for Database Tooling

The purchase order asks for one number and the vendor page offers two shapes, so the question arrives before anyone has opened the trial. DbSchema sells the same Pro and Architect editions both ways, which turns the choice into a budgeting decision rather than a feature one: the perpetual licence is one payment with a year of updates and an optional renewal after that, and the monthly subscription keeps you on the latest release for as long as it runs.

Is a perpetual license better than a subscription?

Buy the perpetual licence when DbSchema is going to stay in the stack and you would rather not re-approve it every year. Buy the subscription when the money has to come out of an operating budget, or when you want every release the day it ships without deciding each January whether it was worth renewing.

The two shapes differ in what stops when payment stops, and that is the line worth reading first. A DbSchema perpetual licence is a "perpetual fallback": buy once, get one year of updates and technical support, and after that you keep forever the version you are entitled to. A renewal after that first year buys the latest features, security fixes, and continued support[1]. A DbSchema monthly subscription gives full access to the latest release for as long as the subscription is active.

Neither shape changes what DbSchema does. Pro is Pro either way, and Architect is Architect either way, so nothing is traded away by picking the one your finance process prefers.

What are the four types of software licenses?

Four models cover almost everything in a development stack, and a single project usually runs on three of them at once.

Permissive open-source licences such as MIT and Apache 2.0 let you inspect, modify, and redistribute the source with little more than an attribution requirement, which is why they carry the least compliance work. Copyleft licences such as the GPL sit in the same family but attach conditions to distribution, so they need reading before you ship anything that embeds the code.

Commercial perpetual is a permanent right to run a specific version of a proprietary binary, usually with updates and support attached for a defined period. Commercial subscription is time-bounded access to the same software with updates and support folded into the recurring fee. Usage-based pricing bills on recorded consumption instead: query volume, compute time, or concurrent connections.

A single team can hold all four. The engine underneath is often permissive open-source PostgreSQL, the DbSchema licence that models its schema is commercial, and the warehouse the reports run against is billed by consumption. The licences you actually choose between for a database design tool are the two commercial ones.

What are the disadvantages of a perpetual license?

One disadvantage is real and the rest depend on the vendor's terms, so it is worth naming precisely rather than in general.

The real one is that updates stop when the included period ends. A DbSchema perpetual licence includes one year of updates and technical support, and a version left without a renewal keeps working but stops receiving the latest features and security fixes[1]. The renewal that removes it is optional and priced at about a quarter of the licence[2]; the figure for each edition is in the table under the decision criteria that matter.

The upfront payment is the other objection, and it is the one the monthly plan exists to answer. DbSchema Pro and Architect are both sold by the month as well, cancellable at any time[2], so a team that cannot get a capital line approved is not blocked from the same features.

Seat rigidity is the third thing usually raised, and DbSchema handles it two ways. A commercial licence is reassigned from the Customer Area when someone leaves, and a team whose use is intermittent buys a floating licence instead, where the purchased quantity caps concurrent users rather than the size of the list[1].

Is a perpetual license the same as owning software?

A perpetual licence is a permanent right to run the software, not ownership of it. The vendor keeps the source, the patents, and the right to decide what ships next; you keep the right to run the build you paid for, under the terms of the licence agreement.

For a database tool that distinction matters in exactly one place: what you are left holding if you stop paying. With DbSchema the answer is the version you are entitled to, running on your own machine, opening the same .dbs model files it always did. The design you built stays readable because the model file is plain XML on your disk[3], so the schema is not hostage to the licence in any case.

What the purchase is tied to is the other thing worth knowing before signing. A DbSchema licence key activates DbSchema on one computer, and moving to another machine means running Help → Unregister on the first one; a machine with no internet access activates offline from the same dialog[1]. Signing in with a DbSchema account is the alternative, and it downloads and activates the licence from an email address with no key file to distribute.

Which licence type a DbSchema purchase chooses between

Besides the edition, a DbSchema licence is described by three more choices, and the pricing page and the licensing page both use these words[1].

The first is user type. A commercial licence is paid for by a company or organization, a personal licence is paid for by an individual out of their own pocket and still allows paid work, and an educational licence is for students and teachers. Only commercial licences can be reassigned to another person.

The second is billing, which is the perpetual fallback and monthly subscription pair above. The third is regular against floating. A regular licence is per person: each seat is assigned to one user by email and used only by that person. A floating licence is per team: a shared pool in which a fixed number of users work at the same time, while the list of allowed users can be as long as you like.

Those three choices are independent of the edition, so a team can hold, for example, commercial floating Pro seats on the perpetual plan.

What is a subscription software license?

A subscription licence is access to the software for as long as you keep paying, with updates and support included in the fee rather than sold beside it.

For DbSchema the monthly subscription means full access to the latest release while it is active, and cancellation at any time[2]. New engine connectors and driver updates arrive without a purchase decision, and a project that ends releases the cost with it. What it does not leave behind is a version you keep, which is the one genuine trade against the perpetual plan, and the reason a team that expects to keep DbSchema for years usually buys perpetual and renews when a release is worth it.

Seat counts are the other reason teams pick monthly. Headcount that moves with contract work is easier to bill monthly than to buy outright, and DbSchema licences are per developer in both plans.

The decision criteria that matter

Four things decide it, and none of them is about the software. How long you expect to keep DbSchema: past about three years, one payment plus optional renewals is the cheaper shape. Which budget the money comes from: capital or operating. How quickly you need new engine support: a subscription delivers it without a purchase order. Whether the design has to work offline, which is a DbSchema Pro capability in either plan, since the .dbs model file lives on your own disk.

DbSchema sells both plans for the same editions, all of which connect to every supported database and keep the design in a local, offline model file that versions cleanly in Git.

All figures exclude taxes and are per developer, read on the Business tab of the pricing page on 6 September 2026. The same page carries a Personal tab and a Universities & Students tab that show lower amounts for the same editions, and it prices in the visitor's own currency, so open it before the purchase order goes out[2]. Community covers all databases, connect and reverse-engineer, interactive diagrams, creating tables and columns, and the SQL editor. Pro adds saving the design to a file, HTML5, PDF and Markdown documentation, schema synchronization, the Query Builder, relational data browse, and the data tools. Architect adds logical and conceptual design.

Settle the edition before the plan, because the plan is the easy half. Download DbSchema at https://dbschema.com/download.html, reverse-engineer a database on the free Community Edition, and let the 15-day Pro trial tell you whether the model file, the documentation export, and schema synchronization belong in your workflow. Those three are Pro, and logical and conceptual design is Architect; the perpetual or monthly question comes after that, and either answer buys the same software.

Frequently asked questions

What is a perpetual software license?

A perpetual licence is a one-time payment for the right to run the software indefinitely, and DbSchema calls its version a perpetual fallback. What the first year includes, and what the optional renewal buys afterwards, is under is a perpetual license better than a subscription.

What is the downside of perpetual software licenses?

New releases stop arriving once the included year ends, while the version already on the machine keeps working. What the renewal costs against the licence, and what the monthly plan answers instead, is under what are the disadvantages of a perpetual license.

Do I own the software if I buy a perpetual license?

A perpetual licence buys a permanent right to run the version you bought, and the vendor keeps the source code and the intellectual property. What a DbSchema licence is tied to, and why the design you built stays yours either way, is under is a perpetual license the same as owning software.

What does a DbSchema subscription include?

The DbSchema monthly subscription covers full access to the latest release for as long as it is active, with the same features as the perpetual licence of the same edition. Technical support comes with it, opened from the Customer Area or from Help → Technical Support inside DbSchema, and the same Customer Area holds the invoices and the licence keys for the subscription.

How much does DbSchema Pro cost?

DbSchema Pro is 294.00 USD one time plus taxes on the Business tab of the pricing page, 196.00 USD on the Personal tab, and 98.00 USD on the Universities & Students tab, all read in US dollars on 6 September 2026 from a page that prices in the visitor's own currency. The monthly price and the optional renewal for each edition are in the table under the decision criteria that matter.

Sources

1. dbschema.com
2. dbschema.com
3. dbschema.com