Support & services

The platform is free.
The crew is for hire.

Roundhouse is Apache-2.0 open source, and the full platform runs without a license key. When MCP servers become something your mission depends on, you want the people who built the turntable on call — for answers, for upgrades, and for the networks where nothing is simple.

Supported by Karmatek · the team that builds Roundhouse
Support tiers

Pick your class
of service

Same software on every tier. What changes is who picks up when something's on fire, and how far into your environment we'll go with you.

Tier 01

Community

For labs, pilots, and teams happy to run it themselves.

Free
Apache-2.0 · open source
  • The complete platform — no feature gates, no license key
  • Field manual and architecture docs, online and bundled for offline use
  • GitHub issues and discussions, answered best-effort
  • Public releases and security fixes
Get started
Tier 02

Production

For teams running Roundhouse in production who need a committed answer, not a best-effort one.

Annual
Per deployment · quoted
  • Everything in Community, plus
  • Private support channel with ticket tracking
  • Next-business-day response target, US business hours
  • Upgrade, deployment, and configuration guidance
  • Direct notification of security advisories
  • Prioritized bug fixes
Request a quote
Tier 03

Enterprise / Federal

For agencies, integrators, and enterprises on air-gapped, disconnected, or otherwise restricted networks.

Custom
Scoped to your mission
  • Everything in Production, plus
  • Severity-based response targets, written into your contract
  • A named engineer who knows your deployment
  • Air-gapped and restricted-network support — registry mirrors, custom CAs, offline builds
  • Hardened-image and non-root runtime guidance
  • Documentation support for your authorization (ATO) package
  • Architecture reviews and a voice in the roadmap
  • Procurement that fits your contracting office
Talk to sales →
CommunityProductionEnterprise / Federal
SoftwareFull platform, Apache-2.0Full platform, Apache-2.0Full platform, Apache-2.0
Support channelGitHub issuesPrivate ticketingPrivate ticketing + named engineer
Response targetBest effortNext business daySeverity-based, set in contract
Coverage—US business hoursUS business hours; extended by arrangement
Upgrade & deployment guidance—IncludedIncluded
Security advisoriesPublic releasesDirect notificationDirect notification + remediation guidance
Air-gapped / restricted networksSelf-serve docsSelf-serve docsSupported
ATO documentation support——Included
Architecture review—Add-onIncluded
Roadmap inputGitHubGitHubScheduled reviews
Purchasing—Invoice / POPO, or through your preferred reseller or prime

Response targets are for initial response, not resolution. Final terms live in your support agreement.

Professional services

Work we'll do
alongside you

Fixed-scope engagements, available with any tier or on their own. Each one ends with something running in your environment and your team able to operate it.

Svc 01

Deployment & architecture

Stand up Roundhouse on Docker, Swarm, or Kubernetes via the Helm chart — TLS, ingress, storage, and backup sorted, with a design your ops team has reviewed.

Svc 02

Air-gapped enablement

Internal registry mirrors, hardened base images, custom CA bundles, and offline image builds — everything needed to run with no route to the internet.

Svc 03

Custom MCP servers

We turn your scripts, APIs, and runbooks into production MCP tools — scoped, documented, and handed over as code your team owns.

Svc 04

Identity & access

Single sign-on with Entra ID or another OIDC provider, role mappings, tool-level scopes, and a token policy that will survive a security review.

Svc 05

Migration & training

Move the MCP servers living on laptops and jump boxes into managed stalls, then train your engineers to build and ship the next ones themselves.

Svc 06

Agent platform advisory

Planning an on-prem agent stack? We help design what sits around the MCP layer — model gateways, agent hosting, identity, and governance.

Federal & restricted networks

Built for networks the cloud can't reach.

Roundhouse deploys inside your authorization boundary. Nothing about it needs to leave.

Hosted MCP platforms assume connectivity you don't have and data flows you can't approve. Roundhouse was designed the other way around: everything runs on your hardware, and the source is open for your security team to read.

  • HostingFully self-hosted. No SaaS control plane, no license server, no phone-home.
  • OfflineWorks air-gapped — internal registry mirrors, bundled docs, custom CA bundles for TLS-inspecting proxies.
  • ImagesSupports hardened, non-root, distroless runtime bases for generated servers.
  • BuildsRootless image builds on Kubernetes, RBAC-scoped, with no Docker socket exposed.
  • AccessOIDC single sign-on, role mappings, per-tool scopes, and tokens encrypted at rest.
  • AuditEvery state-changing action is recorded with the acting user, target, and detail.
  • SourceApache-2.0 — inspect it, scan it, fork it.

Straight talk: Roundhouse is software you run, not a cloud service, so it inherits your environment's authorization rather than carrying its own. We won't claim a certification we don't hold — we will give your ISSO the architecture, data-flow, and configuration detail they need to assess it.

How it works

From first call to
on the line

STOP 01

Talk

A working call with an engineer, not a pitch. Tell us about your environment, your constraints, and what's blocking you.

STOP 02

Scope

We write down the support tier and any services in plain language: what's covered, what isn't, and what done looks like.

STOP 03

Procure

A quote your contracting office can act on — direct, or through the reseller or prime you already work with.

STOP 04

Dispatch

Kickoff, onboarding to your support channel, and an engineer who already knows your deployment by name.

Questions

Asked at the
ticket window

Is Roundhouse still free and open source?

Yes. The platform is Apache-2.0 and every tier runs the same software. Paid tiers buy you people and commitments, not features held hostage.

Do you need access to our network?

No. Most support happens over tickets and screen shares, and for air-gapped environments we work from sanitized logs and configuration you choose to send. On-site work is available by arrangement.

How is pricing structured?

Production support is an annual subscription per deployment. Enterprise / Federal and professional services are quoted against your scope. Tell us what you're running and we'll come back with a number.

Can we buy through an existing contract or reseller?

Usually, yes. Tell us which vehicle, reseller, or prime contractor you prefer to work through and we'll sort out the path with your contracting office.

We only need help once — do we need a subscription?

No. Professional services are available standalone: a deployment, an air-gap enablement, or a batch of custom MCP servers can each be its own fixed-scope engagement.

Who actually answers the ticket?

An engineer from Karmatek, the team that designs and builds Roundhouse. There is no tier-one script between you and someone who can read the code.

Talk to sales

Tell us what you're
running. We'll take it from there.

A short note is enough — your environment, roughly how many servers and users, and what you need help with. You'll hear back from an engineer within two business days.

Or write to sales@karmatek.io