Getting started
Architecture
Hedlo is made of separate apps that share code but never share a process. That keeps a customer session away from staff pages and lets you scale or restart each part on its own.
Apps and ports
| App | Default port | Role |
|---|---|---|
| Bolt admin | 3300 | Staff area for billing, support and setup |
| Bolt client | 3400 | Storefront and client area |
| Loom admin | 3100 | Staff panel, job worker, node enrollment |
| Loom client | 3200 | Customer panel |
| Loom API | 3300 | REST API (/api/v1, /api/client) |
| Shuttle | 8443 (API), 2022 (SFTP) | Node daemon on each machine |
Bolt and Loom both default to port 3300 for one app. When you run them on the same host, change one of them with its PORT setting.
From order to running server
-
A customer orders in the Bolt storefront and pays an invoice.
-
Bolt's provisioning module calls Loom with the plan's resources, location and server template.
-
Loom picks a node in that location and asks its Shuttle daemon to create the container and allocate ports.
-
Shuttle pulls the image, runs the template's install script and starts the server.
-
The customer opens the Loom panel. The console, file manager and resource graphs stream live from Shuttle.
Renewals, suspensions and terminations follow the same path: Bolt decides, Loom applies, Shuttle executes.
Live updates
Every page is rendered on the server and stays connected. When data changes, for example a new ticket reply or a server that finishes installing, the server sends the change and the page updates without a reload. Pages still work without JavaScript; forms post normally.
Data and secrets
-
Bolt and Loom each use their own PostgreSQL database and run migrations when they start.
-
Node tokens, database passwords and integration secrets are encrypted at rest with a vault key that stays on your server.
-
Shuttle keeps server data in
/var/lib/shuttleand never deletes it when the package is removed.
Trust between the parts
-
Shuttle enrolls with a one-time join token created in Loom, then authenticates every request with its own node credentials.
-
Bolt talks to Loom with a scoped API key.
-
Releases, plugins and themes are signed with Ed25519. Each app only loads code signed by a key you trust.