# SparkCR

> SparkCR is a container registry acceleration and caching service for teams. It provides regional cache routing, Docker/OCI image pull acceleration, access-token authentication, private upstream registry support, quota controls, and operational visibility.

SparkCR helps developers and platform teams pull public and private container images through a managed registry endpoint. Use the public documentation links below as the canonical source for setup and troubleshooting.

## Core Pages

- [Home](https://sparkcr.net/): Product overview for SparkCR container image acceleration and cache routing.
- [Pricing](https://sparkcr.net/pricing): Plans and usage model for image caching and team traffic.
- [Network Check](https://sparkcr.net/network): Public IP, peering, quota, and risk-state diagnostics.

## Documentation

- [Quickstart](https://sparkcr.net/docs/quickstart.md): Create an access token and complete the first Docker image pull through SparkCR.
- [Registry Reference](https://sparkcr.net/docs/registry-reference.md): Image reference formats for Docker Hub, GHCR, Quay, GCR, Kubernetes Registry, Elastic, NVIDIA, and private registries.
- [Runtime Configuration](https://sparkcr.net/docs/runtime-config.md): Configure Docker, containerd, Podman, and CRI-O to use SparkCR.
- [Kubernetes](https://sparkcr.net/docs/kubernetes.md): Configure Kubernetes clusters and image pull secrets for SparkCR.
- [CI/CD](https://sparkcr.net/docs/ci-cd.md): Use SparkCR in build pipelines and deployment workflows.
- [Private Registries](https://sparkcr.net/docs/private-registries.md): Configure private upstream registries, pull permissions, and push support.
- [Cache and Usage](https://sparkcr.net/docs/cache-and-usage.md): Understand cache behavior, quota usage, pull history, and rate-limit headers.
- [FAQ](https://sparkcr.net/docs/faq.md): Troubleshoot authentication, 429 limits, image paths, private registry access, and CI failures.

## Usage Notes

- Public image pulls may work anonymously but are subject to anonymous IP quota and risk controls.
- Long-running use, CI workloads, and shared egress networks should authenticate with a SparkCR Access Token.
- Docker Hub official images must include the `library/` namespace when using explicit SparkCR paths.
- Private registry access requires configured private upstream endpoints and tokens with `pull:private` or `push`.

## Excluded Content

Do not treat console, admin, audit, billing internals, risk-control internals, or private workspace pages as public documentation. Public AI-facing guidance should come from the pages listed above.