Infrastructure add-ons for consulting and services engagements

• Managed PostgreSQL — PostgreSQL operations for teams that need safer backups, recovery planning, and visible database health.
• Managed MySQL — MySQL and MariaDB reliability, upgrades, backups, and ownership boundaries for application workloads.
• Managed MongoDB — MongoDB capacity planning, backups, monitoring, and production guardrails for document workloads.
• Managed Redis — Redis operations for cache, session, queue, rate-limit, and real-time data paths.
• Managed Kafka — Kafka reliability, monitoring, retention, and change control for event pipelines.
• Managed OpenSearch — Search and log analytics indexing, lifecycle policies, retention, and troubleshooting support.
• Managed Prometheus — Metrics, alerting, dashboards, and operational signals managed as an observability add-on.
• Managed Runners — Self-hosted CI/CD runner fleets for faster builds, stronger isolation, and predictable local-development parity.
• Managed Git Server — Operated GitLab, Gerrit, Gitea, or Forgejo platforms with clear hosting, identity, backup, upgrade, and runner boundaries.
• Managed Artifact Repositories — Package and build artifact repositories with retention, access controls, and governance.
• Managed Docker Registry — Docker and OCI image repositories operated with tag, retention, access, and scanning workflows.
• Managed Kubernetes — Lightweight Kubernetes support for edge, lab, and constrained environments that still need production habits.

Every add-on starts with an agreed service boundary. Within that boundary, Assistance normally provides:

Cloud provider charges, software licenses, application changes, data modeling, and unlisted platform work are scoped separately unless explicitly included in the engagement. DNS changes, delegated zones, TLS issuance, renewal, and certificate hygiene remain documented supporting responsibilities inside the relevant platform or service scope rather than standalone promoted offers.

Availability targets, response times, exclusions, measurement windows, and recovery objectives are confirmed per add-on and deployment model. We do not apply a blanket uptime promise to systems we have not assessed or do not operate.

Start with an infrastructure assessment. We will map the add-ons you need, the operating boundaries, the deployment model, and the support language required for the engagement.

Request infrastructure assessment →

Is this a replacement for cloud-managed services like RDS, MSK, OpenSearch Service, Cloud DNS, or ACM? Sometimes. We can operate native cloud-managed services in your account, run open-source equivalents on dedicated infrastructure, or use a hybrid model. The right choice depends on cost, control, compliance, and operational requirements.

Who owns the cloud account and infrastructure bill? For customer-account deployments, you own the account and provider bill. Assistance owns the agreed operational responsibilities and charges a service fee for that scope.

Can you migrate existing production data or platform configuration? Yes, when migration is scoped by size, downtime tolerance, compatibility, access, and rollback needs. Data, DNS, delivery-platform, and certificate migrations all require an explicit cutover plan.

Do all add-ons include 24/7 support? No. Monitoring and support are defined by the selected plan. Critical response is available for covered production services, but it is not implied for every assessment or development-only environment.

Can we keep application ownership? Yes. Assistance operates the infrastructure add-on. Your team keeps application architecture, schema decisions, business logic, release timing, and customer-facing product decisions unless a broader service agreement says otherwise.