System Requirements
Honeyframe is packaged as Python services with static frontends, fronted by an nginx reverse proxy. The default deployment runs all services on a single Linux host.
Operating system
- Linux — Ubuntu 22.04 LTS or Debian 12 are tested. Any glibc-based distribution from 2023+ should work.
- macOS — supported for development only.
- Windows — not supported as a host. WSL2 works for development.
Hardware
For a single-tenant install (one organization, one project, dozens of users):
| Resource | Minimum | Recommended |
|---|---|---|
| CPU | 4 cores | 8 cores |
| RAM | 8 GB | 16 GB |
| Disk | 50 GB | 200 GB SSD |
| Network | 100 Mbps | 1 Gbps |
The Python services collectively cap at ~1.5 GB resident under load (MemoryMax=1500M per systemd unit). The remaining headroom is for the database, dbt runs, and the Lakehouse (Parquet + DuckDB) cache.
Runtime dependencies
- Python 3.10+ (3.10.12 tested in production; 3.11+ recommended for forward-compat —
google-api-coredeprecates 3.10 on 2026-10-04). - Node.js 22.x (frontend builds via Vite; the build server's npm workspaces hoist
viteto the monorepo root). - PostgreSQL 14+ (16 recommended). The platform stores its operational data in a
hubstudioschema and its observability data in adataintelschema. - nginx 1.18+ (reverse proxy, TLS termination, rate limiting).
- systemd (services run as systemd units — see Custom systemd Units).
- Certbot (Let's Encrypt issuer; see TLS / Certificates).
Optional dependencies
- dbt 1.7+ — required if you intend to run transformation models. Honeyframe ships dbt templates under
paas/dbt/. - DuckDB 0.10+ — bundled via
duckdbPython package; required for Lakehouse-backed datasets. - Ollama or another LLM provider — required for Agent Builder, Knowledge Bases, and the SQL chat surface. See Connectors for the supported LLM connector list.
Network ports
| Port | Service | Exposed externally |
|---|---|---|
| 80, 443 | nginx | Yes (HTTPS only after Certbot) |
| 8001 | Platform API | No (proxied) |
| 8002 | Cloud API | No (proxied) |
| 5432 | PostgreSQL | No (loopback or VPC-internal) |
The reverse proxy is the only public surface. All API ports listen on 0.0.0.0 for ease of inter-service communication; in a multi-host install, restrict them to the private network with a firewall.
Database
A dedicated PostgreSQL instance is recommended. The platform creates two schemas on first run (hubstudio, dataintel) — give the connecting role membership in both, plus CREATE on the database for migrations.
For multi-tenant installs, allocate one Postgres database per tenant. Tenants do not share schemas.
Browser support
The frontend targets evergreen Chromium-based browsers (Chrome, Edge, Brave) and Firefox 110+. Safari is supported on macOS / iOS 16+. IE and legacy Edge are not supported.