Skip to main content

Stacktic

Version‑controlled automation for full‑stack complexity

Stacktic converts application topology into a fully versioned Git repository—complete with deployment manifests, security policies, and Day‑2 operations. Design your stack visually; we generate the code and keep it in sync.

Why Stacktic?​

FeatureWhat you gain
🚀 Automated relationshipsService links and dependencies are mapped for you—no manual YAML.
🧠 Metadata‑drivenDeclarative metadata eliminates human error and operational drift.
📦 Full‑stack version controlRoll back or branch entire environments, not just code.
🔒 Autonomous securityRBAC, NetworkPolicy, and OPA rules generated at build time.
☁️ Cloud‑agnostic migrationImport workloads from VMs, managed services, or Docker to Kubernetes in minutes.

High‑Level Workflow​

  1. initilze configuration – configure Repo and Regsitry tokens
  2. Design topology – Drag components and connect them.
  3. Generate your stack – Build to create the Git skeleton (k8s/, scripts/, dashboards, secrets).
  4. Deploy Your Stack – Kustomize your full stack on K8s Cluster

Core Concepts​

ConceptDescription
ComponentA service such as backend, PostgreSQL, or Prometheus.
Sub‑componentA unit inside a component (e.g., a DB schema, a Kafka topic).
LinkRelationship between components (backend → DB).
AttributeParameter used for automation (ports, secrets, flags).

Automation Scenarios (Examples)​

TriggerWhat Stacktic generates
Source Code → DatabaseCreates DB & user, injects connection string as Secret.
Grafana → PrometheusEnables metrics, ServiceMonitor, and dashboard JSON.
ArgoCD GitOpsApplication CRs per component for multi‑cluster sync.
Kafka Topic → DatabaseProvisions topic, ACLs, and KafkaConnect sink.
PoliciesRBAC, NetworkPolicy, and OPA Gatekeeper rules via toggles.

Quick Start​

before we start, here is a 3 min video example​

# 1. Sign in
https://staging.app.stacktic.io/

# 2. Create or select a Stack
https://staging.app.stacktic.io/systems

# 3. Configure system (tokens > passwords!) and domain
  1. initilze configuration – configure Regsitry token
alt text
  1. initilze configuration – configure Repo token
alt text
  1. SOPS support (optional) – Enable encryption by adding your Age public key (optional only)
alt text

Designing Your First App​

  1. Drag‑and‑drop a backend and a database, then connect them.
  2. Build (first time) – choose Build, not FastBuild, to create the full repo.
  3. Merge strategy – The stacktic branch is the generated skeleton; main is yours. Automatic merges respect your custom edits.

Deploying​

# Clone the generated repo
$ git clone <your‑stack‑repo>
$ cd <your‑stack‑repo>

# Build & push images (Kaniko jobs)
$ kubectl apply -k k8s/build/overlays/dev/ --server-side --force-conflicts

# Deploy manifests
$ kubectl apply -k k8s/deploy/overlays/dev/ --server-side --force-conflicts

# Verify ingress
$ kubectl get apisixroute -A

Updating & FastBuild​

Use FastBuild when you only tweak component values (tokens, secrets). It captures ~95 % of relationships for the selected service and rebuilds quickly.

# Keep local main up‑to‑date
$ git fetch origin main
$ git checkout main
$ git reset --hard origin/main

Managing Source Code​

OptionBest forHow it works
External source codeFull code ownershipPoint to repo & Dockerfile; Stacktic builds + deploys.
image_baseTeams with custom CIPush your own image; Stacktic handles deploy & config.
Stacktic templates100 % hands‑offUse pre‑built service templates (contact us to enable).

Migrating an Existing App​

  1. Import code (external repo or pre‑built image).

  2. Add databases and links.

  3. Load data:

    • Manual restore
    • MinIO bucket‑based job (recommended)
    • initdb scripts during container start

  4. Validate ingress & health checks.

  5. Add complexity – Airflow, Kafka, RabbitMQ, etc.

  6. Enable Day‑2 Ops – logging (Loki), monitoring (Prometheus + Grafana), autoscaling, security policies.

Examples​

Resources​

Need help? support@stacktic.io

© 2025 Stacktic. All rights reserved. This guide is provided "as is"; test in non‑production environments first.