Services

Service Plans and Pricing

Flat-rate infrastructure plans plus focused audits and custom packages


Pricing is designed around how infrastructure work is actually bought: sometimes you need a short audit, sometimes a fixed-scope project, and sometimes continuous capacity. We define scope, responsibilities, cadence, and deliverables before work begins so costs are predictable.

Pricing options#

Buying modeBest forCommercial shape
Focused auditYou need evidence and prioritization before implementationFixed-scope proposal
Implementation packageYou need a concrete outcome such as a platform, migration, landing zone, or pipeline rebuildFixed-scope proposal
Ongoing service planYou need continuous DevOps, SRE, cloud, or Kubernetes supportFlat monthly plan
Custom engagementYou need regulated, multi-region, high-complexity, or dedicated supportCustom proposal

Ongoing flat-rate plans#

FeatureXSSM
Monthly price€3,000€6,200€9,100
Best forSmall teamsGrowing teamsProduction-critical teams
Support hours8×58×524/7
Engineering levelMiddle+Middle+ / SeniorSenior
Delivery cadenceWeeklyWeeklyWeekly plus urgent response
CI/CD supportBasicAdvancedEnterprise
Infrastructure as CodeAdvisory / light implementationIncludedIncluded
Cloud operationsBasic reviewMonthly governanceAdvanced governance
Kubernetes supportBasicStandardAdvanced
SRE practiceAssessment-orientedImplementation supportManaged reliability support
DevSecOpsAdvisoryIncludedIncluded
Emergency supportSeparate scopeSeparate scopeIncluded within agreed scope
Security auditingSeparate scopeSeparate scope or add-onIncluded or prioritized by scope

Plan cards#

What all ongoing plans include#

Team and cadence#

  • named point of contact
  • shared communication channel
  • weekly planning or review rhythm
  • monthly summary of completed work and next priorities
  • documented backlog and decision points

Delivery and operations#

  • support within the agreed service scope
  • CI/CD, infrastructure, cloud, Kubernetes, or reliability work according to plan fit
  • documentation, runbooks, pull requests, configuration changes, and handoff notes
  • incident or emergency handling according to plan coverage

Governance and reporting#

  • clear assumptions and responsibilities
  • visible scope boundaries
  • monthly evidence of work performed
  • recommendations for larger projects when work exceeds the active plan

Focused audit packages#

Audits are useful when you need evidence before committing to larger work.

AuditBest forOutput
Infrastructure AuditBroad infrastructure uncertaintyExecutive summary, technical report, prioritized roadmap
Security AuditSecurity and compliance riskRisk-ranked findings and remediation plan
CI/CD AuditDelivery pipeline bottlenecksPipeline baseline, findings, and implementation roadmap
Cloud Account AuditCloud cost, IAM, and governance issuesAccount inventory, cost baseline, access review, quick wins
Kubernetes AssessmentPlatform adoption or cluster riskCluster/workload review and recommended service path

Audit pricing depends on system count, access complexity, compliance mapping, and report depth. We scope it before starting.

Implementation packages#

Fixed-scope packages are used when the outcome is clear.

PackageCommon outcome
CI/CD rebuildFaster, safer delivery pipeline with documented release and rollback path
IaC foundationVersion-controlled infrastructure provisioning and review workflow
Cloud landing zoneAccount structure, IAM, networking, logging, policies, and IaC baseline
Kubernetes platform buildCluster, GitOps, ingress, TLS, observability, security, backups, and handoff
Reliability implementationDashboards, alerts, runbooks, incident model, and SLO candidates
Security remediationPriority findings fixed or converted into an owned backlog

How to choose a plan#

If this sounds like you...Choose
You need a clear diagnosis before buying implementationFocused audit
You know the result you need and want it deliveredImplementation package
You need recurring DevOps or cloud capacityXS or S
You need senior production support and 24/7 coverageM
You have strict compliance, high scale, or multi-region requirementsCustom engagement

Onboarding and billing path#

  1. Fit call — confirm goal, urgency, systems, team size, and budget shape.
  2. Scope draft — define services, systems, coverage, deliverables, exclusions, and assumptions.
  3. Commercial proposal — agree audit price, implementation package, flat-rate plan, or custom engagement.
  4. Kickoff — create communication channel, access plan, delivery cadence, and first milestone.
  5. Monthly or final review — review outcomes, evidence, and next-step recommendations.

What affects price#

  • number of repositories, services, environments, clusters, and cloud accounts
  • required support hours and incident-response expectations
  • compliance, security, or evidence requirements
  • migration risk, data sensitivity, and change-control process
  • need for dedicated engineers or senior architecture support
  • custom integrations, multi-region design, or regulated environments

Getting started#

Frequently asked questions#

Are XS, S, and M hourly buckets? No. They are flat monthly service plans with agreed scope, cadence, and support coverage.

Can we start with an audit and upgrade later? Yes. Many teams start with an audit, then move into implementation or an ongoing plan after reviewing the findings.

What is not included in a flat-rate plan? Work outside the agreed scope, major migrations, new compliance programs, and large platform rebuilds are scoped separately.

Can we change plans? Yes. Plan changes are handled at a billing boundary or through a revised scope when the operating need changes.

Do you offer custom pricing? Yes. Custom pricing is common for regulated environments, multi-region systems, dedicated engineers, and formal SLA requirements.