01 / Product
The application is the unit
Web, databases, workers, cache, storage, jobs, configuration, and bindings belong to one Product instead of becoming separate provider dashboards.
Caleb Media Studio LLCInternal systems
Internal platform · built like a product
The system we're building to run Caleb Media.
Constellation is the application and infrastructure platform Caleb Media Studio is building for the software we operate ourselves: GrydBase, CampusLayer, our Web applications, databases, workers, storage, networking, and the releases that tie them together.
The goal is not to hide great infrastructure. It is to stop making every useful piece of it feel like a separate operating system for the company.
- First customer
- Caleb Media
- Application model
- One Product
- Status
- Internal proving
Live topology
Control without an inbound door
Agent
Outbound only
Runtime
Native Web + OCI
Edge
Public by choice
The same thesis, turned inward
Our own infrastructure should not be the exception.
GrydBase is about making fragmented business software feel like one system. CampusLayer applies that idea to schools. Constellation applies it to Caleb Media itself.
Instead of treating Web hosting, data, workers, cache, storage, domains, builds, and infrastructure as unrelated products, Constellation gives the application one model and keeps the provider/runtime detail underneath it.
02 / Placement
Infrastructure stays replaceable
An Environment is compute, not product identity. Workloads can move between Caleb Media-managed, cloud, colo, or customer-owned infrastructure without changing what the application is.
03 / Release
Production gets one answer
Deployments change pieces. A Product Release is designed to describe the complete state that should be production across services, bindings, and runtime placement.
Constellation Web / delivery
A commit becomes a Web Deployment.
A Git commit triggers an isolated Next.js build, produces a framework-aware immutable Web artifact, places its private Node runtime on a selected Environment, and publishes it through the outbound Cloudflare tunnel.
Every deployment receives a managed Constellation hostname. Customer domains add a verified custom-hostname and CNAME lifecycle; the CNAME alone does not mark production ingress ready.
- Web
- DB
- Worker
- Cache
- Storage
- Jobs
- Functions
- Cron
- Flags
Web Deployment / model
Immutable build
- Commit
- 8d91e2f / main
- Build
- Next.js / immutable
- Artifact
- constellation.web@sha256:7f5c…9a21
- Placement
- chosen environment
- Managed URL
- project.constellationcdn.com
- Custom URL
- CNAME + TLS validation
Product Release / production
The Release coordinates the whole Product.
A Web Deployment is one selected service. A Release is the canonical, immutable production asset that selects exact Web, DB, Cache, Storage, Worker, and other service revisions with the binding graph promoted alongside them.
production-2026-08-26
Canonical asset
control-plane
Web
rev_042
primary-east
DB
rev_018
session-cache
Cache
rev_009
events
Worker
rev_031
assets
Storage
rev_014
One application operating model
From source to production without losing the rest of the system.
BUILD
Build with framework context
Next.js can become a framework-aware immutable Web artifact while generic software keeps OCI as the universal runtime escape hatch.
OPERATE
Run the whole product
Logical Web, DB, Worker, Cache, Storage, and job services share one operating model while their underlying adapters stay visible when you need them.
OBSERVE
Keep evidence together
Health, logs, builds, database state, capacity, ingress, and release history can be understood as parts of the same application instead of unrelated provider events.
RECOVER
Design for the bad day
Typed operations, private management, backups, restore evidence, immutable artifacts, and explicit production state make recovery a product capability rather than a collection of runbooks.
Our first customer is us
Built like a product. Proven inside Caleb Media first.
Constellation is not being rushed into a public infrastructure product. We are designing the APIs, security boundaries, portability, auditability, and developer experience like a real product while Caleb Media uses the platform as its proving ground.
The target is simple: we should trust it with our own production software for a long time before asking another company to do the same.
Now
Build the platform against real internal needs.Native Web, managed data, generic runtimes, ingress, releases, and the workflows needed by Caleb Media products.
Next
Move our own workloads when each one is actually ready.GrydBase, CampusLayer, and company systems become the acceptance tests rather than marketing claims.
Later
A public product only after the trust is earned.No artificial launch date. Product-quality software now, external availability when the operating history justifies it.
No magic cloud
Built on infrastructure we can explain.
Constellation is the operating layer, not a claim that Caleb Media reinvented every component underneath it. We use strong infrastructure where it makes sense and keep the application model ours.
CloudflareEdge, DNS, TLS, and outbound application ingress
LinuxThe common Environment substrate underneath workloads
AWS + owned infrastructureDesigned as interchangeable Managed capacity, not application identity
Next.js + OCIFramework-aware Web where we can, generic runtime where we should
PostgreSQL + SupabaseThe first mature Constellation DB implementation
Caleb Media Studio LLC / Constellation