Skip to main content

BuiltForProd Managed

BuiltForProd Managed is optional, recurring DevOps engineering after a deployment: engineers who operate, maintain, secure and evolve your production environment as an extension of your team. It comes in three options, from pay-as-you-go hours to embedded full-time engineers. You build the product; Managed keeps production running.

The three options​

OptionWhat you getCommercial terms
On-DemandOn-demand consultation and support from BuiltForProd DevOps engineers, for when you run into a problem and need urgent assistance. Channels: email, Slack and video conferencingPay as you go, per hour, only when needed; minimum 10 hours
Support SLAThe same on-demand consultation and support, governed by strict, predefined service level agreements (SLAs). Channels: email, Slack and video conferencingFixed, pre-paid per year: a minimum of 100 hours, expiring after one year, reachable whenever needed; saves 30 percent compared with On-Demand
Team AugmentationDedicated DevOps engineers embedded directly in your technical teamPart-time: 4 hours per day, 20 hours per week. Full-time: 8 hours per day, 40 hours per week, saving about 17 percent against part-time. Either option on a 6-month or 12-month commitment, billed monthly; the 12-month commitment saves about 10 percent

The Support SLA figures are set in the customer agreement; the service level agreements page explains how they attach to each option and the SLA definitions page defines the terms.

Which option fits​

  • On-Demand suits a team that operates the platform itself and wants an expert available for the occasional hard problem: an upgrade with a surprising plan, a drift issue nobody understands, a security finding that needs a second opinion.
  • Support SLA suits a team that needs a response commitment: production carries real consequences, and "we will get back to you" is not an answer the business accepts.
  • Team Augmentation suits an organization where production matters but nobody owns it full-time, or where the platform team is a ticket queue and developers wait on it. The engineer joins your channels, your reviews and your on-call rotation under your conventions.

The fit table on what is BuiltForProd points growth-stage companies and any organization without a platform team at Managed.

What Managed works on​

Managed engineers work within the platform as delivered: the same repositories, the same pull-request, plan, review, apply path, the same CODEOWNERS rules and the same groups your engineers use (IAM Identity Center, Microsoft Entra ID or Google groups). Nothing is applied from a laptop and no separate access path is created. The Operable page describes those conventions; the shared responsibility model draws the line between what Managed does and what stays with you.

How to engage​

Managed is purchased directly, or for AWS customers through an AWS Marketplace private offer, like the Baseline and the Blueprints; the steps are on purchasing and licensing. The channels for an active engagement are on contacting support, and the options are restated from the support side on support options.