Concepts
The runtime model: how a System’s declared topology becomes Kubernetes workloads, what a release names, what the GitOps repository contains, and how ArgoCD keeps environments honest.
Run
intropy.run
intropy.run is the runtime half of these docs: what happens after you’ve built a System and need it to run somewhere real. The framework’s output is portable container images and YAML; intropy.run is an open, self-hostable set of conventions for running those artifacts on Kubernetes, with Dapr sidecars, GitOps-driven deployment through ArgoCD, and OpenTelemetry observability. You own and operate all of it, the same as the framework.
The handover between the two halves is an artifact, not a ceremony. The build side ends by publishing a release: an immutable manifest naming a version, the source commit, and the exact image digests CI built for it. Operations move that artifact through environments by editing one GitOps repository: release create, then deploy pin into dev, deploy promote up to staging and prod, and ArgoCD reconciling each cluster toward what the repository declares. Nothing on this side rebuilds anything, and nothing reaches a cluster except through Git.
It is one way to run the artifacts, not the only one. The examples in this tab target Azure Kubernetes Service (AKS) and on-prem clusters; the same images run on OpenShift or any other conformant Kubernetes cluster, and nothing in the build output assumes Kubernetes at all.
If you’re here to build a System — define Components, declare a topology, name Ports — start in the intropy.dev tab instead.
Sections
Section titled “Sections”Deploy
Set up the GitOps repository, publish releases, move digests through the environment ladder, and render the same manifests onto a local cluster.
Observability
OpenTelemetry traces, metrics, and logs from a running System, exported over OTLP to a backend of your choice, with an optional Grafana / Loki / Tempo / Prometheus reference stack.