Octopoda
The business foundation that Data and Distrib sit on.
In brief
Fleet answers "how do I operate my devices". Octopoda answers the other question: what do these devices do, and how does their owner make use of them.
Each customer receives their own space: their database, their sites, their domain, their brand. Their users never see that Arkipelis exists.
Two uses sit on that shared foundation. Data when the machine reports data to be monitored. Distrib when it sells.
They are not two separate products: you switch the second on with nothing to migrate.
What it brings : You open a new customer in minutes, under their brand, with no bespoke development.
In detail
Fleet answers the question "how do I operate a fleet". Octopoda answers the other one: what does this fleet do, and how does its owner make use of it.
Each account receives its own deployment — its database, its sites, its integrations — on a shared or dedicated zone, with its own domain and branding. Data and Distrib are two uses of that same foundation, not two separate products: they share the deployment, the contexts, the permissions, the integration and the alerts.
What the foundation brings
| One-click deployment | An account, a zone, and its whole set of services is raised and then held by convergence — no manual installation, no drift between two accounts. |
| Contexts | A single portal, with scopes: each user sees only their own. A site, a branch, a canteen, a demonstration — the same mechanism. |
| The octopod | The business identity of the point of sale, independent of the hardware fitted to it: the machine changes, the point of sale remains. |
| Site configurable without development | Pages, widgets, languages and labels are settings; code is not the only way to change a screen. |
| The customer's domain and branding | Their portals answer on their domain, in their colours — their users do not see Arkipelis. |
| Integration with the information system | Signed outbound notifications, programming interfaces and connectors: the fleet is not an island. |
| Ingestion, whatever the path | A direct feed from a device or a third-party system, or a deposited file — the boundary is clear and recovery is possible. |
| Multi-channel alerts | Email, SMS, live notification — the alert reaches the person who can act. |
| Fleet health, on the customer's side | The owner sees the state of their fleet in their own portal, without going through the vendor. |
| Hybrid fleet | Points of sale with no Arkipelis hardware enter the same view, through a connector. |
What sets it apart
The same foundation for every account. What is delivered to one customer is what runs for the others: a fix benefits everyone, and a specific need does not make one installation diverge.
Business is configured, not re-coded. Contexts, pages, widgets, languages, domains and notification rules are account settings, not software versions.
Extension stays inside the framework. Code specific to one account sits on the same bases as everything else, with the same deployment cycle: there is no parallel branch to maintain.
The two uses
Octopoda Data
Field data becomes a service: collection, portal, alerts, reports.
Octopoda Distrib
Turnkey automated distribution: catalogue, sales, consumers, field work.
A Data account can switch Distrib on with no migration; a Distrib account has Data. Everything that takes payment forms Octopoda Pay, the payment option of Distrib or a product sold on its own.