( _products )

Two products.
One engine.

Deployment models describe target architectures subject to project validation. The current ALLINLET Edge module provides configuration registration and export; an installable collector, signed updates and fully isolated runtime are not yet delivered.

Both run on the ALLINLET Engine, with the same 900+ connectors. The difference is who operates it and where your data lives.

FULLY MANAGED

ALLINLET Cloud

We run the connectors. Your application receives the data.

  • Operations, monitoring and updates handled by our team
  • Reaches devices on your internal network through ALLINLET Edge
  • Data delivered via API or other channels agreed with you
  • No servers to manage, and no need to use our interface
  • Data retention policy defined in your contract
BEST FORTeams that want the data, not the infrastructure.
PRICINGSubscription by sources, data volume and service level.
Get started with Cloud
IN YOUR INFRASTRUCTURE

ALLINLET Enterprise

Our engine, in your infrastructure. Your data, under your control.

Collection, processing and storage all happen inside your environment. Readings never leave your network. Choose how it operates:

OfflineFully air-gapped: no internet and no external access. Signed updates, installed by your own team.
ConnectedReceives only the updates you approve. No remote access by us and no readings sent out.
Assisted SupportSUPPORT OPTIONTemporary remote access, opened and controlled by you, for a single intervention. Works with Offline or Connected.
PRICINGLicence or subscription per installation and capacity, plus maintenance and support.
Talk to our Enterprise team
FOR CLOUD AND ENTERPRISE

ALLINLET Edge

Data collection on every site, managed from one place.

Most equipment lives on internal networks with no direct internet access. Today, ALLINLET Edge is a configuration registry: define each customer site, its sources and destinations, and export the configuration with an integrity checksum. The installable on-site collector is in development and is not yet delivered.

  • Your devices stay on your internal network, never exposed to the internet
  • Data only goes to the destinations you authorise
  • Buffering and resend rules recorded per site, for the on-site collector to apply
  • Planned: contact and status reporting once the on-site collector is available
Ask about Edge
YOUR SITE · INTERNAL NETWORK
PLCs Meters BMS Sensors Historians
ALLINLET Edgelocal collection
Your internal systemshistorian · SCADA · data lake
ALLINLET CloudAPI · streams · ALLFLOW
CUSTOMERS & SITESEvery site, organisedGroup Edges by customer, factory, building or park, with an identified owner for each site.
EDGE IDENTITYRegistered per siteEach Edge has a name, a unique identifier and an association with its site.
CONNECTORS & SENSORSThe right sources, per EdgeChoose the sources each Edge collects from the catalogue, with their local settings.
DATA DESTINATIONLocal, cloud or bothInternal systems only, ALLINLET Cloud, or both, exactly as you authorise.
OPERATIONResilient by designCollection intervals, temporary local storage and resend rules for unstable links.
STATUSAlways know it's workingLast contact, installed version, connector status and the latest reading received.
( _side by side )

Which one fits you?

Feature Cloud Enterprise
Who runs the engineThe ALLFLOW teamYour team, backed by our support
Where it runsOur infrastructureYour infrastructure
How it reaches field devicesThrough ALLINLET Edge on your site, outbound onlyDirectly, or through ALLINLET Edge at each site
Where readings goDelivered to your applications, under your contracted policyThey stay in your network, always
UpdatesAutomatic, managed by usInstalled by you (Offline) or approved by you (Connected)
Remote access by ALLFLOWNot applicableOnly via Assisted Support, opened by you
Commercial modelSubscriptionLicence or subscription
( _the engine )

The ALLINLET Engine

The same engine powers Cloud and Enterprise. Every reading goes through four stages, whatever its source.

  1. 01CollectNative connectors read each source in its own protocol, on its own schedule.
  2. 02ValidateReadings are checked for structure, type and completeness before they move on.
  3. 03NormaliseEvery reading is mapped into one consistent model, whatever the source protocol.
  4. 04DeliverClean data goes to your APIs, streams and databases, or straight into ALLFLOW.
( _getting started )

From first call to live data

  1. 01Book a demoTell us which systems you run. We show ALLINLET working on a case like yours.
  2. 02Run a pilotConnect your first sources with a fixed scope and see your own data flowing.
  3. 03Go liveScale on Cloud, or deploy Enterprise in your own infrastructure.
( _the allflow ecosystem )

From raw data to Digital Twin

ALLINLET is where real-world data enters ALLFLOW Business Intelligence. Use it on its own, or as the foundation for Digital Twins and AI-driven simulation.

01 · DATAALLINLETCollects and normalises real-world data.
02 · MODELDigital twin platformA live digital replica of your assets and processes.
03 · DECISIONAI simulation platformScenarios, forecasts and optimisation before you act in the field.

Not sure which fits?

We'll help you choose between Cloud and Enterprise based on your sources, security policy and team.

Talk to us

Explore deployment options

ALLINLET Cloud: managed data integration target architecture

How ALLINLET Cloud is intended to ingest, normalise and route industrial and IoT data in a managed environment, with prerequisites, data handling and current limitations.

Explore →

ALLINLET Enterprise: self-hosted integration in your infrastructure

Target architecture for running ALLINLET Enterprise inside your own data centre or private cloud, including prerequisites, responsibilities and limitations.

Explore →

ALLINLET Edge: configuration registry and export for site gateways

What ALLINLET Edge provides today: a registry of site source configurations with export for gateways. No installed agent, signed releases or offline runtime are delivered.

Explore →