Skip to main content

What's pre-integrated — and why

ExplanationPublic

The problem this solves

Building a secure, compliant DevSecOps platform from scratch means integrating 40–60 tools. Each needs to talk to every other, be hardened to your compliance baseline, packaged for air-gap delivery, and maintained when a CVE drops. Doing this yourself takes 6–18 months.

SmoothGlue ships all of it pre-integrated, pre-hardened, and pre-tested.

How pre-integration works

When you run smoothglue install, the CLI:

  1. Pulls a Zarf package containing all selected apps and their dependencies — no internet required after this step
  2. Deploys each app using its tested Helm chart
  3. Wires apps to the Keycloak SSO instance automatically — GitLab, ArgoCD, Jira, and Mattermost all use the same identity provider with no manual OAuth configuration
  4. Applies Kyverno policies to enforce zero-trust network rules between all apps
  5. Configures the observability stack to scrape metrics from every app automatically

What SmoothGlue handles for you

CategoryToolsWhat you don't configure
Source ControlGitLabOAuth2 to Keycloak, GitLab Runner, Iron Bank image pull
CI/CDArgoCD, GitLab CIArgoCD RBAC, GitOps repo sync, pipeline templates
IdentityKeycloakSSO for all apps, FIPS-compliant login
Artifact RegistryNexusPull-through cache, Iron Bank proxy
ObservabilityPrometheus, Grafana, Loki, Tempo, AlloyAll scrape configs, dashboards, alert rules
SecurityKyverno, NeuVector, AuthServiceZero-trust network policy, runtime behavioral analysis
SecretsVaultVault-Agent sidecar injection, lease management
CollaborationJira, Mattermost, ConfluenceSSO, notifications, webhook wiring
Air-gap deliveryZarfPackage creation, offline install, image mirroring

What you still own

  • Your application code and its Helm charts
  • Your domain names and TLS certificates
  • Your AWS/GCP/Azure account and IAM permissions
  • Your application-specific secrets (database passwords, API keys — stored in Vault, but created by you)

Learn more