Security and deployment

Your plant. Your data. Your network.

FluxAI360 deploys on-premise or in your own cloud account; quality data never has to leave the plant. It is read-only by default, and nothing outside needs a way in.

Deployment options

Two ways to run it. Both are yours.

Plant server

On-premise

Everything runs on a server inside your plant network. Nothing needs to leave the building.

Your tenancy

Your cloud account

The platform runs inside your own cloud account, in the region you choose, under your own access policies.

On-premise or your cloud

Runs on a server in your plant or inside your own cloud account. You own the infrastructure.

Read-only by default

Any write-back, such as a line stop, is configured only where you ask for it.

No inbound access

No inbound internet connection is required. Nothing outside reaches into your OT network.

In-region data

Data stays in the plant, or in the cloud region you choose. Quality data never has to leave.

Where data flows

Inside your network, by design.

Your plant network
01 · Sources
Industrial camerasGigE / USB3 vision
Existing vision systemsresults, images, CSV
Machines and PLCscycle, state, parameters
Inspection dataCMM, gauges, logs
ERPSAP S/4HANA and others, via APIs
Documents and drawingsreports, drawings, invoices, POs
02 · Edge
Edge collectorread-only taps · on site
  • Vision inference at the station
  • Read-only by default
  • Image and machine data capture
03 · Platform
Plant server or your cloudyour hardware or your account
  • Sealed per-part records
  • Versioned spec limits
  • Models and history
04 · Outcomes
Dashboardsquality, OEE, drift
Reports and documents8D, summaries, validation
Planningforecasts, stock-outs
Assistantanswers with sources
Alertsdrift, stoppages, daily summary
No inbound internet required
Controls

What your IT and OT teams will ask.

Data residency

Data stays in the plant, or in the cloud region you choose. Quality data never has to leave the plant.

Read-only by default

Read-only by default; any write-back, such as a line stop, is configured only where you ask for it. ERP access is read-only through backend APIs.

No inbound connections

No inbound internet connection is required. No port on your OT network has to be opened to the outside.

Access control

Role-based access, so operators, quality engineers and managers see what their role needs.

OT-friendly

Designed to sit beside the line and your ERP without replacing anything. Production does not depend on it to run.

Advisory by default

It advises the operator by default, and can stop the line through your PLC when you want it to.

Need detail for a security review? Write to deepak@fluxai360.com and we will walk your IT and OT teams through the deployment.

Start with one station

Tell us which defect costs you the most.

We will tell you honestly whether it can be imaged and inspected reliably, what a pilot would look like on your line, and what we would measure.