Deployment Tiers
Honeyframe ships in three deployment tiers. The product is the same across all three — same UI, same recipes, same connectors. What changes is who runs the infrastructure underneath.
Choose your tier
| Tier | Who runs the infra | Best for | How to get it |
|---|---|---|---|
| Honeyframe Cloud | We host it on our infrastructure | Teams that want to start fast without provisioning servers — pilots, evaluations, small deployments | Sign up at app.honeyframe.io (coming soon), click Create Space, pick a region |
| Honeyframe Enterprise | Customer's own cloud account (BYOC), we deploy and manage | Enterprises with data-residency, procurement, or networking constraints that require Honeyframe to live inside their cloud | Contact sales — engagement-led |
| Honeyframe Self-Hosted | Customer, on-prem or their own VM | Air-gapped environments, regulated industries, or teams that need full operational ownership | Tarball + license file + setup-customer.sh |
What you get is the same
Every tier provisions a Space — a managed Honeyframe instance scoped to your organization. A Space contains your projects, datasets, recipes, dashboards, users, connections, and dbt models. Whether the Space runs on our infrastructure (Cloud), in your cloud account (Enterprise), or on your own server (Self-Hosted), the application layer is identical.
This means you can start on Cloud, outgrow it, and migrate to Enterprise or Self-Hosted later without rewriting recipes or rebuilding dashboards. Project export/import is preserved across tiers.
What this manual covers
This Documentation section is written primarily for Self-Hosted, because Self-Hosted operators need every detail — system requirements, reverse-proxy config, TLS, LDAP, systemd units, license activation, and so on.
If you are on Honeyframe Cloud, most of the Installation chapter does not apply to you — we run the install for you. Skip to Connectors, Datasets, and Recipes to start building.
If you are on Honeyframe Enterprise, your account team will have already deployed Honeyframe into your environment. Use this manual to understand operational behavior; defer infrastructure changes to your account team.
Common questions
Can I move between tiers?
Yes. Spaces are portable: project bundles, recipe definitions, dashboards, and dbt models all export to a tier-agnostic format. The data underneath your connectors stays where it is — Honeyframe doesn't move your warehouse. Migrating tiers means standing up a new Space on the target tier and re-pointing connections.
Is Honeyframe Cloud multi-tenant?
Each Space is provisioned as a single-tenant instance — your data is not co-mingled with other customers. The "Cloud" label refers to who operates the instance, not how data is isolated.
What region is Honeyframe Cloud hosted in?
At launch: Jakarta (Indonesia). Additional regions will be added based on customer demand. Enterprise tier customers choose their own region — it's their cloud account.
How does pricing work?
Cloud has self-serve pricing (free trial → paid tiers). Enterprise and Self-Hosted are both license-based — contact sales for a quote tied to your seat count and node footprint.
Where to next
- New to Honeyframe? Read the Overview and try Quickstart.
- Installing Self-Hosted? Start with System Requirements and Standard Install.
- Already have a Space? Jump to Connectors to bring in your first dataset.