Commercials

Licensing and support

Open core, drawn along an honest line: the part you build with is free and Apache-2.0, including in production. The part an organisation needs in order to govern what it built is licensed.

What is free

The generator, the MCP server emission and the com.mcpdbwizard.pub runtime library that generated code links against are licensed under the Apache License 2.0. Take them, fork them, run them in production, ship products built on them.

Code emitted by the generator is your own work and carries no licence obligation from this project. It links at run time against the Apache-2.0 runtime library, so generated applications may be distributed under any terms you choose. The open module has no parent POM and no dependency on anything proprietary in the repository — it can be copied out on its own and built, which is what makes the grant real rather than nominal.

What is licensed

The control plane: the Design and Runtime web application, the configuration store, curation, the accounts and access matrix, and the MCP proxy that authenticates callers and records what they did. Proprietary, all rights reserved.

The split follows what each part is for. A developer connecting an agent to a schema needs the generator, and should have it for nothing. An organisation putting a language model in front of a production schema needs to answer a different set of questions — which tools exist, who is allowed to call them, who called what and when — and that is what the licensed half is built to answer.

How it is priced

Per production MCP server, annually. Non-production is free.

Why that unit and not another:

• It matches how the thing is actually deployed — one server per curated schema.
• It is countable and auditable without instrumenting a customer's estate.
• Per-seat is wrong: there are almost no human users. The callers are agents.
• Per-database is worse: it invites an argument about what counts as a database in a multitenant estate.

Free non-production is not generosity — it is how you build the thing that later needs governing, and it keeps the open-core promise honest. Develop, test and evaluate for as long as you like at no cost.

This is an enterprise licence sold direct, usually with implementation work alongside it, rather than a self-serve subscription. Talk to us and we will quote against the number of production servers and the support level you need.

What a licence includes

Version-currency assurance

This is the part worth paying for, and the part a fork cannot supply itself.

MCPDBWizard is certified against Oracle 12c, 18c, 19c, 21c, 23ai and 26ai — six live instances, re-verified on every release of this product and against new Oracle releases. Generated output is compared version by version, file by file, so a change that quietly stops emitting code on one release is caught here rather than in your environment.

The question a regulated buyer actually has is not "does it work". It is "will it still work after we patch to 23ai in March, and who is accountable if it does not." That is what this answers.

Support and indemnity

Support with a response commitment, from the people who wrote it. Indemnity terms, and source escrow where procurement requires it.

On the standard objection — what happens if you are hit by a bus — the structural answer is that the generator is Apache-2.0 and you already have it. The commercial answer is escrow and a support contract. Both are offered; neither substitutes for the other.

The control plane itself

The Design and Runtime web application, multi-account access control, the authenticating proxy and its access records, OAuth 2.1, and the durable audit trail with its write-ahead spool.

What we are honest about

Two things a buyer should hear from us rather than discover.

Authorization is per config, not per tool. The access matrix decides which configs an account may drive. It does not map roles to individual tools at run time, and that is a design decision rather than a gap: two teams needing different tools over one schema is two configs, and an object left out of a config has no code generated for it at all. We consider enforcement by absence stronger than a rule in a running process, and we are not going to weaken it into one.

What you select is exposed as written. A selected delete tool deletes. The product's job is to make the selection reviewable, generated faithfully and recorded — not to second-guess the selection.

Talk to us

Evaluations, quotes, DB2 or other-database enquiries, and design-partner conversations in regulated verticals: info@mcpdbwizard.com.

Oracle and PL/SQL are trademarks of Oracle Corporation. This project is not affiliated with Oracle.