Product documentation

What the Arkipelis platform does, described product by product.

In brief

Arkipelis provides the platform on which you build your connected offering: machines in the field, and the applications that drive them and make them sell.

It comes as two applications. Fleet handles the devices: building them, deploying them, keeping them alive from a distance. Octopoda handles the business side: the data they report, and selling when the machine sells.

You do not start from a blank page: the application framework, the building blocks and the hosting are provided. Your teams write only what sets you apart.

What it brings : You launch your offering in weeks, you operate it with a small team, and your end customers see only your brand.

In detail

Arkipelis builds an integrated platform to build, deploy and operate connected applications on fleets of devices. It is hosted on the customer's cloud infrastructure, and comes as two twin applications.

Both share a single model: shape and default values come from the account's Git repository, live settings from the database, and secrets from the vault. One account is enough to enter both.

Who it is for

Companies that want to build, and not merely operate, connected applications characterised by:

  • a physical presence — shop, factory, point of sale, distribution site;
  • a touch interface or a full-screen display;
  • specific hardware: payment, sensors, inputs and outputs, audio, screens;
  • periodic synchronisation with the cloud — exports, telemetry;
  • deployment across several sites, with audit and compliance requirements;
  • often several accounts: reselling to several brands, chains or end customers.

All of it without starting from a blank page on the application framework, the base modules and the integration work.

The six pillars

Launching in weeksThe application framework is provided: teams write only the business logic. Ten base modules, six languages, and the same code from the developer's machine to the field.
Operating at scaleDeploying means pointing to a version, with a preview of what changes. Each device is driven from the browser, and the embedded foundation updates itself.
Never breaking the fieldThe device boots and runs without a network, a failed update rolls itself back, the firewall is closed by default, and a device's identity survives its replacement.
The customer's brandScreens and portals carry their identity, down to their own domain name. Accounts are isolated by construction, and the console speaks seven languages.
Cost or sovereignty, as you chooseShared, for a near-zero marginal cost, or deployed on the customer's own hosting so their data stays with them. Moving from one to the other rewrites nothing.
Partners without exposing the platformEach integrator works in their own autonomous repository, with no access to the core, and proprietary code is never distributed in the clear.

What the platform covers

  • Running data: a portal per account, dashboards, alerts, users, scopes per organisation, ingestion by file or directly, anomaly detection, analysis.
  • Distribution and the connected point of sale: catalogue and offers published to machines.
  • Sales authorised on the spot and validated by the cloud, with accounts, badges and subsidies.
  • Field operations, reports, consumer site and recipe machines.
  • White labelling, down to the device screens, the portals and the customer's own domain.
  • Field work without a network: configuration over a USB cable and technician access by certificate, offline, with no rewriting.
  • The payment terminal as a device: fitting out an existing machine, as companion to a box or standalone.
  • Payment: certified terminal, till systems, accounts and vouchers, outbound notifications to the customer's system.
  • Remote system updates: security patches without rewriting cards.
  • Dedicated zones on several hosting providers: portability by construction.

What it leaves to others

This boundary is deliberate: these are not gaps to be filled, they are choices. They point towards the right complementary tools.

  • Not open source: the core remains Arkipelis property — the customer's business code remains the customer's.
  • Neither industrial supervision nor maintenance management: the platform complements them, it does not replace them.
  • Not a cloud provider: it is hosted on the customer's cloud, who keeps control of it and of its costs.
  • Not an identity provider: it relies on a third-party directory, with federation available.
  • No low-level hardware management: no modem firmware, no power supply, no board firmware.
  • No bank card processing: payment goes through a certified terminal or a provider; the platform carries accounts, vouchers and subsidies, never a card number.
  • No fine-grained location tracking and no mobile device tracking.
  • Neither a full continuous integration chain nor a management suite: integrators keep their own tools.

Who does what

RoleScope
ArkipelisBuilds and maintains the platform — application framework, base modules, agent. Supports the integrator and the customer, and provides the Octopoda suites according to the subscribed facets.
The integrator (internal or partner)Develops the business modules in their own autonomous repository, on the provided framework, with no access to the core. They use the base modules without modifying them.
The end customerOperates their console — fleets, deployments, monitoring, data — hosts their cloud infrastructure, and manages their devices and their business.

Contents

This documentation is produced from the Arkipelis product base. It describes the capabilities of the platform.