FREQUENTLY ASKED QUESTIONS
Everything you need to know before installing RunRight in your CI pipeline.
No. It polls /proc every 5 s as a background sidecar. Under 5 MB RSS, under 0.1% CPU on the sampler. Your build time is not affected.
No. RunRight wraps your existing CI step. No SDK, no annotations, no config file required.
No. Use --export otlp with OTEL_EXPORTER_OTLP_ENDPOINT pointing at your existing collector. The backend and Postgres are only needed for the self-hosted RunRight dashboard.
Yes. RunRight reads cgroup v2 (cpu.max, memory.max) or cgroup v1 equivalents to reflect the pod's actual CPU quota and memory limit. You can also pass RUNRIGHT_VCPUS and RUNRIGHT_MEMORY_GIB via the Kubernetes Downward API if you prefer explicit values.
RunRight samples system-level metrics from your CI runner: CPU usage, memory (RSS), disk I/O, network I/O, and thread count. These are written to your workflow artifacts and stay on your infrastructure. Nothing is sent to RunRight's servers. If you configure --export otlp or --export http, metrics go to a destination you specify.
No. The AI assistant runs entirely on your infrastructure. Point it at a local Ollama instance or any OpenAI-compatible endpoint you control. Your job history, cost data, and telemetry never leave your servers.
Use the built-in role system under Settings → Roles & Permissions. Assign Owner, Admin, Billing, Developer, or Viewer roles to any SSO user from the dashboard. Custom roles let you combine any set of the eight permission scopes — no restart required to apply changes.
Google Workspace, GitHub OAuth, Azure AD (Microsoft Entra ID), Okta, any generic OIDC provider, and enterprise SAML 2.0. SSO is configured entirely from the dashboard — no config file changes or restarts required.
Yes. Every create, update, and delete action is recorded with the actor's email, timestamp, and a diff of changed fields. Alert rule changes are tracked at the individual rule level — modifying one rule doesn't produce audit noise for unchanged rules.
A Go binary and a Postgres database. The included Docker Compose file brings everything up in one command. No cloud account, no managed service, no external dependencies beyond what you run yourself.
Yes. The helm/ directory in the repository includes a Helm chart for deploying the backend and connecting it to an existing Postgres instance. A prebuilt container image is available on Docker Hub.
Not currently. RunRight is self-hosted only. This keeps your telemetry on your infrastructure and eliminates per-seat or usage-based pricing. See the pricing page for details.