Assistance documentation overview

This documentation app helps readers understand Assistance services and the operating model behind them. Use it to find the right service guide, confirm shared responsibilities, prepare onboarding details, and route support or security-sensitive requests.

Assistance is presented from a Bulgaria/EU origin through the assistance.bg domain family. Treat that as brand and operator positioning unless a page ties a stronger regional, residency, compliance, support, or availability claim to a concrete deployment model, provider evidence, or signed engagement.

Start with the service path#

Use Getting started for the high-level service map and claim boundaries.
Read Supporting Infrastructure Add-ons when evaluating managed databases, delivery platforms, observability, DNS, certificates, runners, or supporting infrastructure.
Use Managed runners when CI/CD capacity, isolation, private-network access, or runner operations are the main need.
Read the shared responsibility model before production-impacting delivery or operations work.
Keep support and security workflows nearby for intake, escalation, evidence, and documentation feedback.

Documentation areas#

Getting started and overview: where to begin, what Assistance offers, and which claims require evidence.
Infrastructure: managed databases, Git platforms, artifact repositories, DNS, certificates, observability, containers, Kubernetes, and landing-zone guidance.
Runners and delivery: self-hosted CI/CD runners, release readiness, migrations, GitOps, and delivery operations.
Security and compliance readiness: access control, secrets, incident response, evidence collection, and customer-led compliance review support.
Local development and operations: development parity, environment expectations, monitoring, telemetry, and operational runbooks.
API, SDK, and reference material: generated and authored reference docs backed by the specs under apps/docs/spec.
Support and troubleshooting: request routing, escalation expectations, and issue diagnosis.

How to read service pages#

Service pages are written around the same questions:

What does the service do?
When is it a good fit?
What does Assistance operate?
What does the customer own?
Which deployment, support, residency, or compliance claims need separate evidence?
What should the reader do next?