Components
Each component lives in its own repository; the names follow the particles of the standard model.
Higgs — Orchestrator
Orchestrator: deployment API, scheduler, TLS ingress, authoritative DNS, ACME, Raft state, stack bootstrap, file locks, application-to-service tokens.
The Higgs boson is the excitation of the Higgs field, the field that gives mass to the other elementary particles. It was observed at CERN in 2012.
Higgs, the orchestrator, is the field everything else relies on: it gives each application its place and its weight in the cluster.
Strange — Node agent
Node agent: runs applications as isolated systemd units, networking, the /distributed/* gateway, lock relay. An application can be a plain executable or a .tar.gz archive (executable, libraries, system packages per distribution that the agent installs). It drops the application-to-service tokens in a read-only file of each instance and renews them.
The strange quark (s) is a second-generation quark with an electric charge of −1/3. The gluon is the boson of the strong force: it binds quarks together.
The agent binds each application to its node, as gluons bind quarks together.
Rup — Storage
Storage nodes: SHA-256 content-addressed objects, replicated files, quotas.
The up quark (u) is the lightest quark, with a charge of +2/3. A proton contains two of them; this is the red one.
Storage is one of the two up quarks of the proton: a foundation the other components build on.
Bottom — FUSE daemon (C)
FUSE daemon in C (libfuse3): file locks between nodes.
The bottom quark (b) is a third-generation quark with a charge of −1/3, a heavier cousin of the down quark (observed in 1977).
The low layer of the file system: the daemon under the /distributed/* mounts.
gDown — Graph database
Replicated graph database (Raft): charm, top, metadata; openCypher and Bolt; applications reach their own database over TLS Bolt (Bolt + OGM supported).
The down quark (d) has a charge of −1/3. A proton contains one, together with two up quarks; this is the green one.
The graph database is the largest quark of the logo: the memory the platform rests on.
Top — Config & secrets
Top: per-application configuration and secrets, Vue web interface.
The top quark (t) is the heaviest known elementary particle (about 173 GeV/c²), with a charge of +2/3.
Top keeps the heaviest thing a platform holds: secrets.
Charm — Identity provider
Short-lived JWT issuer (ES256) and minimal OIDC provider.
The charm quark (c) is a second-generation quark with a charge of +2/3, observed in 1974.
The identity provider gives each program the short-lived “charm” that makes it recognised.
Bup — Builder
Builder: Git clone, native build, publication, deployment. When the native build produces libraries, the application is published as a .tar.gz archive (executable, libraries, system dependencies per distribution). The Maven repository of Sea, where the platform SDK is published, is added to its Maven and Gradle builds, alongside Maven Central, so a customer application that depends on the SDK builds without any setting. It passes the services an application declares (uses, dedicated gDown database) on to the orchestrator.
The second up quark of the proton; this is the blue one. The three quarks of a proton carry three different colours that cancel out.
The builder turns your code into the artifact that gets deployed.
Photon — API gateway
API gateway and message processing. Routing by domain and path, per-domain certificates, policies (addresses, CORS, charm token, rate limits) and gDown exposure run in Higgs, the orchestrator; this component handles signed webhooks, JSON/XML/form/ProtoBuf transformations, a persistent queue and delivery with retries, on several replicas.
The photon (γ) is the massless boson of electromagnetism: it carries light and, with it, information.
The API gateway is the front door through which the light of the outside world, its requests, enters the cloud.
Field — Static content server
Static content server: sites are deposited as a ZIP and served from /distributed/std/<uuid>/ ; the site is chosen by a signed header set by the ingress, never by the client.
A quantum field is a quantity defined at every point of space; particles are its excitations.
Static content, the matter, is made available everywhere on the network by this application.
Gauge — AI pilot (MCP)
MCP server: lets an AI assistant deploy, configure and read the logs of applications through the platform API. Per-application charm tokens with limited roles, rules defined by the client, human approval for production, full audit of every action. A read-only usage tool reports the memory and CPU of the applications and of the platform's components (a snapshot, never a billing basis).
Gauge bosons are the particles that mediate the fundamental forces. They are the concrete manifestation of gauge symmetries, which define how matter particles interact with each other.
The interface carries a force: it lets the AI act on the cluster, but that action is filtered and authorised by the gauge law the client has set (the MCP configuration), just as a gauge boson is bound by the symmetry that defines it.
Calorimeter — Observability
Observability: keeps the logs and metrics of every application beyond the life of a node, with a dashboard per application and alerts. It builds on what Higgs and Strange already expose: journals, /q/metrics, and Prometheus discovery at /metrics/sd.
A calorimeter is a particle detector that measures energy by absorbing particles layer after layer: the energy they deposit reveals what went through.
The activity of every application deposits its energy in the calorimeter as logs and measures: it absorbs them, records them, and lets you read what happened.
Synchrotron — Admin console
Administration console: a native Quarkus service serving a Vue 3 interface. It validates the Charm token and forwards each call to the platform APIs (Higgs, Top, Charm, Photon, Bup) with the caller's own token, through an allow-list: it never raises privileges.
A synchrotron is a circular particle accelerator: magnets bend the beam while an electric field adds energy at each turn, until the particles reach the wanted energy.
Like the control room of an accelerator, the console lets the operator inject energy into the platform (deploy, scale, wake) and watch the beam, never beyond the rights of the person using it.
Sea — Release store
Release store (images.gluonify.io): serves the signed native binaries that install.sh and Strange download. Content-addressed files, immutable releases; the Ed25519 signature of the manifest, checked by the client, is the root of trust, and a version can never go back (sequence number). It also serves the platform's Maven repository (/maven/): public read, publication reserved to the platform publisher, released versions immutable. The Java SDK for customer applications is published there, and the builder adds this repository to its builds.
Inside a proton, besides the three valence quarks, a « sea » of virtual quark–antiquark pairs and gluons keeps appearing and disappearing: it is a large part of what the proton is made of.
The sea surrounds the quarks that make up the proton; here the store surrounds the platform with the binaries it is made of, and every node draws from it what it installs.
Fermion — Workflow & rules engine
Workflow and rules engine: BPMN 2 workflows and DMN decision tables, kept in Git (Bitbucket, GitLab) and run on the server side. Applications connect as nodes over a permanent WebSocket (the protocol and a client are in the plasma SDK), announce their skills and only execute atomic tasks; Fermion routes the steps, retries, timers and circuit breakers, and resumes a failed execution at its last step. State and history are in gDown; calls are authenticated with Charm tokens; web interface in Vue, in five languages. A single active replica for now. Sending messages (email, Teams, post) is left to Interfero, a node like any other.
A fermion is a particle with half-integer spin that obeys Pauli's exclusion principle: two identical fermions cannot occupy the same quantum state. Quarks and electrons are fermions.
A workflow and rules engine lives under the same constraint: at any moment an instance occupies a single step, a task is given to a single node, a decision returns one deterministic answer for a given payload. Hence the rigour of the engine.
Crystallon — Document conversion and generation
Document service: it turns a dynamic document into a fixed, self-contained, archivable one, and it generates new ones. Conversion: images (BMP, JPEG, PNG, TIFF, WebP) become PNG; PDFs become PDF/A-1B (fonts and colour profile embedded, XMP metadata) and several PDFs can be merged into one; nothing is kept. Generation: a PDF is produced from a JSON template and JSON data (invoice, quote and letter presets, Swiss QR-bill with strict validation, PDF/A-1B on request). Templates are kept per organisation in a dedicated gDown database, with versions, history and restore, together with their logos and images (SVG images are drawn as vectors); an application renders a template by its name, or at a given version, and every validation error says where it is in the template. A graphical editor in the web interface (English, French, Spanish, Italian and German, light and dark theme) lays the page out: blocks added and moved by drag and drop, text in styled segments, columns, the Inter and Helvetica fonts, live PDF preview with sample data. Each organisation can also upload its own TrueType fonts (licence checked, rights confirmation required, four variants per family, quotas): templates use them like the built-in ones and they are embedded in the PDF/A-1B. Its Code tab gives an application what it needs: the schema of the data the template reads (JSON Schema) and generated Java code, records and a facade built on the Java SDK, which is distributed through the Maven repository of Sea. Access is by Charm token (audience gluonify-crystallon) with one role per job: render to generate documents, convert to convert them, templates to manage them. An application that declares crystallon in its uses receives a short-lived render token from the platform, renewed without a restart; a signed-in person can also forward their own. Payment-provider secrets are read from the Top vault. Conversion of AVIF and HEIC images is done by external tools (avifdec, heif-convert) that must be installed on the node; without them the service answers 503. It ships as an application archive with its libraries.
A crystal is a solid whose atoms sit in a regular lattice repeated in every direction: a liquid that cools settles into this fixed order.
The service does the same to a document: a photo, a PDF produced by any tool or several PDFs to assemble are set into a stable format that depends on no reader.
Interfero — Message sending
Message sending: a native REST API (Quarkus, Charm tokens, state in gDown) that gathers email (SMTP), Teams (Workflows webhook), six messaging apps (WhatsApp Business through Meta's Cloud API with approved templates, Telegram, Slack, Discord, LINE, Viber; credentials per organization in Top, official hosts only) and postal mail (PDF rendered by Crystallon, then handed to a postal provider; only a spool provider exists so far, no real postal carrier) behind one interface. It is a Fermion node announcing SEND_MSG_EMAIL, SEND_MSG_TEAMS and SEND_MSG_POST, and it keeps the message templates (versions, preview, sending log); the Templates view is in Fermion. Its calls to Crystallon and Fermion use the application tokens the platform provides, with nothing to configure.
An interferometer superposes waves coming from several sources and reads the pattern they make together, which shows what a single wave could not.
The API superposes several channels (email, Teams, messaging apps, postal mail) into one interface, as an interferometer combines several waves into one reading.
The cluster
How the components fit together. The numbers in the diagram match the list below.
- Visitors reach your application through Higgs: HTTPS with automatic certificates, and the DNS names it serves.
- Higgs and every Strange agent keep a WebSocket open: Higgs sends the desired state and the secrets, the agent reports health.
- Higgs forwards each request to a ready instance on its node (Photon, Field or your application); for a static site it adds a signed header naming the site.
- Strange starts each application as an isolated systemd unit, in its own network namespace.
- Applications, Photon and Field included (Field reads the sites there), read and write /distributed through Bottom (FUSE) and rclone.
- Files are stored in several copies on the Rup storage nodes.
- Applications use the platform services: gDown for data, Charm for identity tokens, Top for configuration and secrets.
- Charm and Top keep their data in gDown, with keys and secrets encrypted.
- Bup clones the Git repository where your code is kept, written by you or by an AI assistant.
- Bup builds the native executable and asks Higgs to deploy it.
- An AI assistant drives the platform through Gauge (MCP).
- Gauge acts on Bup and Higgs with limited Charm tokens, inside the rules set by the client.
- The Calorimeter keeps the logs and metrics that Strange collects from every application and that Higgs exposes, and turns them into dashboards and alerts.
- The Synchrotron is the administration console: it calls the Higgs API (and the other services) with the signed-in person's own token.
- Sea, outside the cluster, serves the signed binaries that install.sh and Strange download to install and update the nodes.
One address for every interface
Higgs can serve the whole platform behind a single address, for example https://gluonify.lan: the console, the tools and the sign-in page share one host, each under its own path prefix.
- Higgs is the reverse proxy of that address: routes by path prefix, the longest prefix wins, a route / is the default, and a policy (auth, cors, limits, ips) can be set per route.
- The apex of the zone is a domain: only the name exactly equal to the zone is accepted, names such as api.gluonify.lan or an application's name under the zone stay reserved for the API and the applications. Its certificate is the certificate of the zone (apex and wildcard), obtained through ACME; no second certificate is ever requested for the apex.
- Development routes of kind upstream: Higgs calls a target address (http or https) directly, with no Higgs application, placement or node, for a development cluster whose interfaces are JVMs on the machine. HTTP, HTTPS and WebSocket are relayed, X-Forwarded-* headers and the prefix are set, and a stopped target gives a JSON 502. In a real cluster the tools are Higgs applications.
- Targets of upstream routes must lie in an allow-list (loopback and private networks by default), checked when the route is saved and at every call; cloud metadata addresses are always refused.
- Single sign-on: Charm sits at the root of the address and its session cookie is the single session. Each interface makes a silent exchange (OIDC prompt=none) and shows Charm's sign-in page only when no session exists. Sign-out is single too: Charm ends the session from an id_token_hint and a registered return address.
- Tools menu: the shared package gluonify-ui provides AppSwitcher, a drop-down menu to jump between interfaces, placed beside the language and theme controls. It reads the public catalogue GET /portal/apps.json served by Synchrotron and shows only the tools whose required roles match the roles of the signed-in person. This filter is a convenience: every service still enforces its own rights.
Documented in the READMEs of Higgs and Charm. Limits: an HTTPS target of an upstream route is checked against the authorities of the JVM (not covered by an automated test); there is no periodic health probe, the state of a target shows at call time (502).