Custom contracts

When 9 servers aren't enough.

Higher server limits, custom diagnostic recipes, dedicated onboarding. Same engine as Deployment Crew, fitted to your stack.

10+ servers (talk to us about exact count)

Custom diagnostic recipes for your stack

Direct working contact with the mttrly team

Email the team

What's in a custom contract

Everything Deployment Crew gives you, plus the bits we tune for you directly.

Higher server limits

Crew caps at 9 servers. We negotiate the right number with you and provision accordingly.

Custom diagnostic recipes

The 9 stock recipes (website-down, high-latency, post-deploy-issue, disk-full, server-errors, change-audit, server-setup, pre-deploy-check, post-deploy-verification) cover most cases. If your stack has a recurring failure mode that the standard recipes miss, we build a recipe for it.

Direct working contact

Agree the practical communication path with the people who built the product. The exact channel and response expectations belong in the contract, not in a generic website promise.

Custom onboarding

We help you connect your servers, set up deploy profiles, and walk through the first incident together.

What we don't promise (yet)

mttrly is in active development. A few things you might expect from an "enterprise" tier are not in the product today, and we won't pretend otherwise.

  • —SOC 2 / HIPAA / formal compliance certifications
  • —SAML / SSO authentication
  • —Role-based access control (RBAC)
  • —Container-isolated execution environments
  • —Contractual retention guarantees beyond the current service policy

These are on the roadmap, but we don't have firm dates. If any of these are hard requirements for you, we'll say so on the call instead of selling you a plan that doesn't fit.

Common questions

~ How is this different from Deployment Crew?+
Crew is a self-serve product with hard limits — 9 servers, no custom recipes. A custom contract starts where Crew ends: you need more servers, you have a specific failure mode that needs a tailored recipe, or you want a direct line to the team. It's the same agent, the same Central, just sized to your scale.
~ Can AI fix issues without human approval?+
A separately authorized Investigation session lets an AI client use mttrly_execute_command without per-command 2FA inside explicit server, time, and action-count limits. Approval-required actions normally wait for a human; narrowly configured preauthorization is the other bounded, audited exception. mttrly does not hand the AI an unrestricted production shell.
~ Do you support my stack?+
The installer explicitly supports systemd-based Ubuntu, Debian, CentOS, RHEL, Fedora, Rocky Linux, and AlmaLinux. Common workloads include Docker, Docker Compose, Node.js, Python, Go, PHP, nginx, and certbot. Other distributions or managed platforms need a compatibility check; a custom recipe cannot compensate for an unsupported runtime or missing agent access.
~ What about pricing?+
Custom contracts start above Deployment Crew ($99/mo) and scale with server count and recipe complexity. Email hello@mttrly.com with your server count and recurring incident pattern so we can confirm fit and quote the work.

Tell us what Crew does not cover

Email the shape of your setup and the incident work that keeps repeating. We will tell you whether the current product and a custom contract fit it.

If we're not — we'll say so.

Tell us how many servers you run, what repeats during incidents, and what Deployment Crew does not cover.

Email hello@mttrly.com

Direct contact with the mttrly team. No form that disappears into a queue.