Business Central Sandboxes · Invite-only early access

Same product. Two paths.

A Business Central sandbox in under 15 minutes - through the portal for the person typing their email, or through the CLI for the agent typing on their behalf. Same Platform API, same environments, same prices. We're in invite-only early access: join the waitlist and we'll bring you in as slots open.

Portal · For the human

Type your email.
Spin up a sandbox.

For consultants, trainers, sales engineers, and anyone evaluating BC. No CLI, no Azure subscription, no Kubernetes. Pick a version and a region, get a URL in under 15 minutes.

Agent · Sandbox CLI

Hand bcdock
to your agent.

For developers, CI pipelines, and AI agents driving BC work for you. Same Platform API as the portal - single static binary, stable exit codes, --output json on every verb.

$ bcdock env create --version 27 --country au --wait
env env_8h3k2m ready
CLI reference ↗docs.bcdock.io/cli
Prices in
<15m
click → BC sandbox running
from US$0.4/hr
active · Starter+
from US$0.012/hr
hibernated · all tiers
~15m
resume from hibernate
About sandboxes
What you get

A full Business Central container - your data, your code, isolated, with HTTPS access in under 15 minutes.

What it's for

Development, testing, training, demos, and CI. Hibernate between sessions and pay only the low stored rate while paused.

What it isn't

Not production. Not for regulated data. Not a Microsoft product - we use BC sandbox container images.

Sandbox API · Same as the portal

Your agent has the same sandbox surface you do.

When Claude or Copilot runs bcdock, it hits the same Platform API every portal button calls. No private endpoints, no second-class surface.

Every verb supports --output json. Every async operation has --wait. Every error has a documented exit code.

CLI reference ↗
~/al-extensionBC 27 · AU
$ bcdock auth login
# OTP exchange — mints an API key

$ bcdock env create --version 27 --country au --wait
# returns when running

$ bcdock env publish my-env ./MyExtension.app
# multipart POST to /dev/apps, returns when install completes

$ bcdock env hibernate my-env
# drops to stored rate — resume any time

 env_8h3k2m hibernated · saving ~US$0.39/hr
Who it's for

Built for the people who live in Business Central.

BC consultants

Spin up client sandboxes without losing hours to Azure setup.

ISVs and QA teams

Test across versions and localizations on demand.

Accounting firms

Evaluate BC in a safe sandbox before committing to production.

Training providers

Create class-ready sandboxes quickly, then delete when done.

Sales engineers

Tailored BC demos in minutes. Different version, country, or industry per prospect. Hibernate after the call — ready for the next one.

ISVs in CI/CD

Spin up a fresh BC environment per PR. Publish your extension. Run tests. Tear down. All from your existing pipeline.

How it works

Three steps.

01

Join the waitlist

Tell us who you are. During early access we invite people in waves and email you an invite code.

02

Activate and configure

Use your code to create your account, then pick your BC version, region, and localization.

03

Spin up your sandbox

We provision it in about 15 minutes with HTTPS access. Hibernate it between sessions.

Clear on compliance.

BCDock is for sandboxes. Production workloads require Microsoft BC SaaS. Here's the line, row by row.

 BC SaaS (Microsoft)BCDock
Workloads
Production workloadsAvailableSandbox only
Development & testingSupportedPrimary use case
Training & demosNot a fitHibernate between sessions
Per-PR CI environmentsNot designed for thisSpin up · test · tear down
Operations
Automatic BC updatesMicrosoft-managedUser-managed
Power Platform integrationFull supportLimited
Custom code & extensionsAppSource + sideloadSideload anything you build
Compliance
Regulated data (HIPAA, PCI...)In scope (with config)Use synthetic data
Data residency controlPer Microsoft regionsUS · AU

Architecture-level security, written honestly.

Each customer's environments are isolated from everyone else's, secrets are held in regional key vaults, every connection is encrypted, and provisioning activity is kept in a log that can't be edited after the fact. The full posture page - written for procurement and security-questionnaire reviewers - describes what's shipped today and the line between "in the architecture" and "audited by a third party."

FAQ

Questions, grouped.

Pricing, product, compliance, setup - searchable, with the honest answers.

Read the FAQ →
BCDock | Business Central Sandboxes