Application
Docker or Kubernetes/Helm
An environment-configured production container; Kubernetes ingress, secrets, and rollout connect to organizational platform standards.
Self-hosted deployment
Application, metadata, and artifact data stay in your infrastructure.
Smart Kubaba runs as a Spring Boot application with a production Docker image and Kubernetes/Helm deployment. PostgreSQL stores metadata and operation records; filesystem or S3-compatible storage holds artifact content.
Data
PostgreSQL + filesystem/S3
Metadata and audit live in PostgreSQL; artifact content lives in the selected storage component. The two layers require separate backup and recovery plans.
Integration
Identity + network + telemetry
LDAP/Google/OIDC, TLS/DNS, system proxy/egress, application logs, and health endpoints are configured in the target topology.
A verifiable deployment plan
- 01
Define the workload
Formats, package traffic, artifact volume, scan frequency, user model, and network egress.
- 02
Document responsibility boundaries
Owners for PostgreSQL, storage, TLS, ingress, identity, backup, restore, upgrades, and secrets.
- 03
Run acceptance scenarios
Native client flows, access, proxy security, storage transfer, backup/recovery, and operational visibility.
High availability requires shared PostgreSQL, common storage, session/topology, and platform components to be designed together. No public ready-made capacity, RTO/RPO, or SLA profile is published.
Technical evaluation
Evaluate your package flow on Smart Kubaba.
Let’s review your formats, deployment, and security policies together.