Skip to main content
Your origin stack compiles into per-customer installs. Each install is shaped by the ingress posture, controller-connectivity path, and customer-provided services declared at appliance setup time. Tensor9’s customization model is a compile-time agreement between you and each customer. At appliance setup time, your customer declares a small set of properties about their environment, and the compiler emits a deployment stack that honors those properties. Your application code does not change between customers. Three customization surfaces are available:
SurfaceWhat it controls
Ingress postureHow end users reach the deployed application (public, allowlisted, Tailscale).
Controller connectivityHow the appliance reaches your control plane (public internet, AWS PrivateLink, Tailscale).
Customer-provided servicesWhich managed services the install uses your customer’s existing instance of, instead of provisioning a default equivalent.
You author a form factor that defines the permitted set of choices; your customer (or you on their behalf) picks from what the form factor allows at appliance setup time. For per-surface detail pages, the relationship with service equivalents, and supported third-party services (Tailscale, AWS PrivateLink, Temporal, PostgreSQL, MongoDB, Redis, Valkey, Kafka, Elasticsearch family including Lucenia), see Customizations.