Service Onboarding Checklist

Use service onboarding to bring applications onto the platform with clear ownership, safe deployment, and production support expectations.

Required metadata

Each onboarded service should have:

• Service name and description.
• Owning team and escalation path.
• Business owner or product owner.
• Repository, artifact, and deployment links.
• Runtime platform and environments.
• Data classification and compliance scope.
• Cost center and required tags.
• Support hours and on-call expectations.

Delivery requirements

• Build pipeline exists and records artifact identity.
• Deployment pipeline is defined as code.
• Rollback or disablement path is documented.
• Required tests and checks run before deployment.
• Secrets are sourced from approved secret stores.
• Infrastructure changes are reviewed and traceable.

Operations requirements

• Health endpoint or equivalent runtime signal.
• Dashboard for traffic, latency, errors, and saturation.
• Alerts tied to user impact or SLOs.
• Runbook for common failure modes.
• Incident severity and escalation path.
• Backup, restore, and retention expectations where applicable.

Security requirements

• Workload identity or scoped credentials.
• Least-privilege access reviewed.
• Dependency and container scanning enabled.
• Sensitive data handling documented.
• Public endpoints reviewed for authentication, authorization, and rate limiting.

Completion

A service is onboarded when the owning team can deploy, observe, rollback, and support it without relying on undocumented platform team knowledge.