Self-Hosted Scalekit Deployment

Guardrails

• MUST point the app at the self-hosted SCALEKIT_ENVIRONMENT_URL (https://app.<your-domain>), not app.scalekit.com.
• MUST NOT send registry tokens, SMTP credentials, or Postgres/Redis credentials in plaintext or commit them to version control — pass them as Kubernetes secrets / Helm --set-file values.
• MUST NOT confuse the plugin's tooling MCP (https://mcp.scalekit.com, used only for setup guidance) with the self-hosted app's own auth service — the tooling MCP stays cloud-based; the app's SCALEKIT_ENVIRONMENT_URL is what runs air-gapped/on-prem.
• MUST ask the decision-flow questions one at a time before recommending eval vs. production steps.

These reference files ship next to this SKILL.md under references/ in the skill package. Open them with the file tool (absolute path under the installed skill dir, or relative from this skill folder):

• references/quickstart.md — Evaluation deployment (bundled databases)
• references/production-deployment.md — Full production steps, setup script, and portal flow
• references/configuration.md — values.yaml field reference and examples
• references/troubleshooting.md — Diagnostics and fixes
• references/upgrades.md — Upgrades and maintenance

If a references/*.md path is not readable in this session, tell the user and fall back to the high-level steps in this file plus Scalekit distribution docs.