The Console
A single application to drive the products.
In brief
The Console is the single screen from which the platform is driven. Devices and business live side by side: you do not change tools when you change subject, you change tab.
It speaks seven languages, shows the progress of long operations instead of making people wait, and lets each person see only their own scope.
Its distinctive trait: it displays what the system has measured, not what it was asked to do. A version served, a machine last seen at a given time — never an intention.
What it brings : Your teams work in their own language, on a single tool, and every action leaves a verifiable record.
In detail
The Console brings together Fleet — the devices and their deployments — and Octopoda — the business side of the fleet. You do not change tools when you change subject: you change tab.
It is the surface, not one more product: what you do there are the capabilities of Fleet and Octopoda. Its own value lies elsewhere, in what it makes possible whatever capability you are using.
What it brings, across every product
| Seven languages, including Arabic | Right-to-left writing included. The operator works in their language, not in ours. |
| Long operations followed live | A deployment, an image build, a convergence: you see where it stands, instead of waiting with no sign. |
| Permissions by scope | Teams and roles: everyone sees and acts on what concerns them — and a refusal is stated, rather than returning an empty page. |
| The company's sign-in | Accounts come from the customer's directory; nobody maintains a duplicate list of users. |
| The record of what was done | Actions are recorded append-only — you can answer "who did what, and when". |
| The same screen for a real or virtual device | Monitoring does not distinguish hardware from simulation: what you learn on one holds for the other. |
What sets it apart
It shows state, not intent. What is displayed is what the system has measured: a version served, a convergence completed, a device seen at a given time. A tick box that recorded the intent rather than the result would be a defect, not a shortcut.
It knows how to say no. A refused permission is announced as such, with its reason. The user is not left to conclude from an empty page that there is nothing to see.
The distinction, and it is a decision. A missing permission shows greyed out — that is who you are. An absent capability does not show at all — that is what the product is here. We never show the door to a room that does not exist in this offer. The server remains the judge: displaying grants nothing.
It opens inside the page next door. The Console can be framed inside another site — a customer's portal, a demonstration — already authenticated and bounded to the visitor's scope.
Two applications, one model
Fleet and Octopoda are twins: the same model — shape and default values in the account's Git repository, live settings in the database, secrets in the vault — and the same unit of override, the device. The difference is the ground: Fleet drives devices reconciled one by one, Octopoda a shared deployment whose override is read live.
Access is uniform: one account is enough to enter both, and authentication and teams are shared. Security is not an option per application: identity carried by the caller, isolation never derived from content, append-only traceability, explicit failure — that is the foundation.
The Fleet application
Dashboard, fleets, devices, images, scripts, hardware, repositories, credentials, tasks, profile. Screen by screen: The Fleet application.
The Octopoda application
| Page | What you see and do |
|---|---|
| Dashboard | The state of the account's Octopoda deployment: convergence, modules, sites and databases. |
| Deployment | Its identity — environment, zone — resynchronisation, state per module, the shared database read-only, the account's own resources (database, storage, secrets), the override read-only and the history. |
| Modules | The catalogue crossed with state and override: "enabled" and "running" switches applied within seconds, a configuration per module, a "customised" badge and a reset. Subscribed facets are read here too. |
| Data | The data modules with a widget per type: a site leads to its real address on the customer's domain, a database gives its resource, and the custom domain's state shows the records to create and the certificate's status. |
| Tasks | As in Fleet, filtered to the deployment. |
Platform administration
Beyond the two products, the Console carries what supports them: accounts and their teams, the zones — shared or dedicated — hosting, and the licence that decides which facets are active. This is where a dedicated zone is created inside the customer's own cloud subscription, and where Fleet or Octopoda are then deployed onto it. The detail: Hosting and deployment.
The Console's conventions
- Seven languages including Arabic in full mirror layout, with the selector in the header.
- A stable vocabulary: account, fleet, device, application, override.
- Authorisation before display: what is outside the scope does not exist.
- Anything long is a task, with its progress shown live.
- Light or dark theme, and a layout that adapts to mobile.