Skip to content

Validibot Self-Hosted Editions

Validibot is available in three self-hosted editions: Community (free, open source), Pro (commercial license), and Enterprise (for large organisations).

Philosophy

Community is for individuals. Pro is for teams.

The Community edition gives you full access to Validibot's validation capabilities, including advanced validators. Run simple validations (JSON Schema, XML Schema, custom CEL statements, etc.) and advanced validations, explore the results, prove the tool works for your use case. There's no restrictions on what you can validate.

The Pro edition adds team collaboration features, guest access management, and commercial support.

Community Edition

The Community edition is licensed under AGPL-3.0. You can use it freely for any purpose, but modifications must be released under the same license.

Run the full self-hosted application:

Start with the Installation Guide. The recommended self-hosted path uses Docker Compose with just commands for day-to-day operations.

If you're embedding Validibot as a Python dependency for development or integrations, you can also install the package directly:

pip install validibot

That direct package install is for embedding Validibot in Python workflows. It does not provision the full self-hosted web application by itself.

What you can do:

  • Validate FMUs, configuration files, and other technical artifacts
  • Use all validators, including advanced simulation-based validators
  • Build and test custom validators
  • Integrate into your own tools and scripts (under AGPL terms)

Pro Edition

Pro is for teams who need collaboration features and commercial support.

Pricing: $195/month per organization (up to 3 users)

What you get:

  • Everything in the Community edition
  • Up to 3 users — Pro is a small-team starter tier; teams that grow past 3 users move to Enterprise
  • Commercial license — Use Validibot without AGPL obligations
  • Team management — Invite team members with role-based access control
  • Guest access — Let external collaborators (clients, partners) submit data and view results on workflows you share with them. Guests don't count toward your seat cap, but their workflow runs are billed to your org.
  • Verifiable Credentials — W3C Verifiable Credentials 2.0 issued for validation results, signed with your deployment's key so downstream verifiers can confirm the result without trusting the signer's infrastructure
  • MCP server — Connect AI assistants (Claude, Cursor, etc.) to your workflows via the Model Context Protocol. The MCP container ships in the community repo but only accepts traffic when a Pro license is active.
  • Priority email support — Direct access to the maintainers

Purchase: validibot.com/pricing

Setting up Validibot Pro

After purchasing, we'll email your package credentials right away. To view those same credentials on your License Dashboard, create an account using the same email address you used during checkout, then verify that email address.

The dashboard stays locked until email verification is complete. This protects paid licenses from being claimed by someone who only knows the purchase email address.

Before you start

Make sure you have all three of these:

  • the email address used during Stripe checkout
  • the credentials email from Validibot
  • a verified account at validibot.com using that same email

Once that is done, follow these steps to install and activate Pro features.

Step 1: Get your exact package reference

The private package host is pypi.validibot.com. The /simple/ part is only the standard PyPI Simple API path used for package-index installs.

The strongest install reference is the exact wheel URL shown in your purchase email and on your License Dashboard after you verify the purchase email on your account.

"https://YOUR_EMAIL:YOUR_API_KEY@pypi.validibot.com/packages/validibot_pro-X.Y.Z-py3-none-any.whl#sha256=<hash>"

Quote this value if you put it in a shell command or .build file because #sha256=... is treated as a comment by many parsers.

If you prefer package-name installs instead of an exact wheel URL, configure pip for the private index and pin an exact version:

Run this once to save your credentials globally:

pip config set global.extra-index-url https://YOUR_EMAIL:YOUR_API_KEY@pypi.validibot.com/simple/

Set these in your shell profile or CI environment:

export VALIDIBOT_USER="your-email@example.com"
export VALIDIBOT_PASS="your-api-key"

Then reference them in your requirements.txt:

--extra-index-url https://${VALIDIBOT_USER}:${VALIDIBOT_PASS}@pypi.validibot.com/simple/
validibot-pro==X.Y.Z

Step 2: Install the package into your Validibot environment

Choose the option that matches how you run Validibot.

Copy the optional build file if you have not already:

cp .envs.example/.production/.docker-compose/.build .envs/.production/.docker-compose/.build

Then set the exact wheel URL from your dashboard or email:

VALIDIBOT_COMMERCIAL_PACKAGE="https://YOUR_EMAIL:YOUR_API_KEY@pypi.validibot.com/packages/validibot_pro-X.Y.Z-py3-none-any.whl#sha256=<hash>"

If you prefer package-name installs instead, pin the exact version and keep the private index URL separate:

VALIDIBOT_COMMERCIAL_PACKAGE=validibot-pro==X.Y.Z
VALIDIBOT_PRIVATE_INDEX_URL=https://YOUR_EMAIL:YOUR_API_KEY@pypi.validibot.com/simple/

Update config/settings/base.py in the next step, then rebuild Validibot with just docker-compose bootstrap for a new install or just docker-compose deploy for an existing deployment.

Copy the optional local build file:

cp .envs.example/.local/.build .envs/.local/.build

Then set the exact wheel URL from your dashboard or email:

VALIDIBOT_COMMERCIAL_PACKAGE="https://YOUR_EMAIL:YOUR_API_KEY@pypi.validibot.com/packages/validibot_pro-X.Y.Z-py3-none-any.whl#sha256=<hash>"

Or use the pinned package-name form:

VALIDIBOT_COMMERCIAL_PACKAGE=validibot-pro==X.Y.Z
VALIDIBOT_PRIVATE_INDEX_URL=https://YOUR_EMAIL:YOUR_API_KEY@pypi.validibot.com/simple/

Update config/settings/base.py in the next step, then rebuild the local stack with just build and start it with just up.

Install the exact wheel URL into the same Python environment as Validibot:

pip install "https://YOUR_EMAIL:YOUR_API_KEY@pypi.validibot.com/packages/validibot_pro-X.Y.Z-py3-none-any.whl#sha256=<hash>"

Or use the private index with an exact version pin:

pip install validibot-pro==X.Y.Z

Step 3: Add the Django app to INSTALLED_APPS

Add the commercial app in config/settings/base.py.

INSTALLED_APPS += ["validibot_pro"]

If you purchased Enterprise, add both apps instead:

INSTALLED_APPS += ["validibot_pro", "validibot_enterprise"]

Step 4: Restart or rebuild Validibot

Restart or rebuild after you update settings.

Step 5: Run migrations if needed

If your deployment does not automate migrations, run:

python manage.py migrate

Installing the package is the license. Adding the Django app to INSTALLED_APPS activates it for that deployment.

Note

You can verify Pro is active by checking the edition badge in the Validibot footer or by running validibot --version.

Enterprise Edition

Enterprise follows the same installation flow as Pro, but uses the validibot-enterprise package instead.

Setting up Validibot Enterprise

Use the same private package credentials and install flow shown above, but replace the package reference:

  • In Docker or local .build files, use the exact Enterprise wheel URL from the dashboard/email, or VALIDIBOT_COMMERCIAL_PACKAGE=validibot-enterprise==X.Y.Z with VALIDIBOT_PRIVATE_INDEX_URL=https://YOUR_EMAIL:YOUR_API_KEY@pypi.validibot.com/simple/
  • In a direct Python environment, install the exact Enterprise wheel URL or run pip install validibot-enterprise==X.Y.Z after configuring the private index
  • In Validibot settings, add both validibot_pro and validibot_enterprise to INSTALLED_APPS

Enterprise includes Pro as a dependency, so you do not need to install both wheels manually. You should still add both validibot_pro and validibot_enterprise to INSTALLED_APPS so Django loads both apps.

Installing validibot-enterprise is the license. No runtime Enterprise license key is required.

Frequently Asked Questions

Can I evaluate Pro before purchasing?

Yes. The Community edition includes all validators — you can prove the validation logic works for your use case locally. Pro adds team collaboration and commercial support.

If you need to evaluate the full Pro feature set, contact us for a trial license.

What if my Pro license expires?

You can continue using the version you have installed, but you won't be able to download updates or reinstall. Renew your license to restore access.

Do you offer Enterprise pricing?

Yes. The Enterprise edition includes everything in Pro plus: dedicated account manager, SSO/SAML integration, multi-org management, unlimited users, and custom onboarding and training. Contact us at enterprise@mcquilleninteractive.com.

I have AGPL compliance questions

If your legal team has concerns about AGPL, the Pro commercial license removes those obligations.

Support