Commercials

Licensing and support

There is a free tier that is not a trial, and a licensed tier bought annually. Underneath both, the generator itself is Apache-2.0 and yours to keep.

The two tiers

The free tier is not a trial and does not expire. One running server and a real audit trail you can download — enough to put a curated MCP server in front of a production schema and operate it. Nothing switches off after thirty days.

Author as many configurations as you like — that is deliberate, because a second team wanting a different set of tools over the same schema should get a second configuration rather than one over-permissive config shared between them. What the free tier does not do is scale to an estate: running more than one of them at a time is what a licence is for.

What is free and Apache-2.0

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. That grant is unconditional and is not affected by which tier you are on.

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 proprietary, and what that does and does not mean

The control plane is proprietary, all rights reserved: 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 is not the same as paid. You get the whole console on the free tier — every screen, the access matrix, the proxy. What the licence raises is the limits in the table above, not the number of features you can see. We would rather sell you capacity you have already outgrown than a feature you were shown and denied.

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 several production schemas needs to answer a different set of questions — which tools exist, who is allowed to call them, who called what and when, and can we still answer that three months later — and that is what the licensed tier is built to answer.

How it is priced

An annual licence, quoted against the number of MCP servers you run at once. Contact us for pricing.

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.

This is an enterprise licence sold direct, usually with implementation work alongside it, rather than a self-serve subscription. Tell us how many servers you expect to run and what support level you need, and we will quote.

What a licence includes

Audit that survives the question being asked late

The free tier keeps 24 hours, which answers "what happened this morning". A licence lets you set any window up to 90 days on the server and stream records to Kafka, Splunk, S3 or syslog — what you need when the question arrives from an auditor a quarter after the fact, or when the record has to live somewhere the audited process cannot reach. You can also set the window to zero, so nothing is kept on the box at all and the stream is the only copy.

Both tiers record argument names by default and values only if you turn that on. At the values level the trail holds production data chosen by a model, which makes it a personal-data store with retention and erasure obligations — you are the data controller, and the retention window is your control. See setting up auditing.

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.

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: [email protected].

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