Agriculture
Each farm's data, served under the same decision.
Flexway serves the application side of farming platforms: publishing to your MQTT broker under an AsyncAPI contract, streaming measurements to dashboards, sending each partner only its tenant's events, keeping sensitive AI requests on your internal model. It runs on your infrastructure; it replaces neither the field gateway nor the controllers that drive irrigation.
What Flexway decides, on your infrastructure
Who calls, what Flexway decides, what is called: each route is a use case of your sector. Dashed: what is coming.
Architecture for agriculture: farm apps and an agronomy assistant go through Flexway, on your infrastructure. Flexway publishes under contract to your MQTT broker, where telemetry arrives through your field gateway, relays real-time streams to dashboards, sends partner systems, from the broker, signed webhooks limited to their tenant's events, pins sensitive AI requests to your internal model and holds each caller's rate and quota in front of your irrigation services. A caller over its quota gets a 429. Connecting devices directly over MQTT is coming.
- Farm apps
- The applications that call your APIs: each request goes through Flexway, which checks the contract and the identity before reaching your systems.
- Agronomy assistant
- An AI assistant: it calls the models through Flexway's OpenAI-compatible surface, under budget and policy routing.
- Broker events
- A broker whose messages Flexway consumes to deliver them to your partners as signed webhooks.
- MQTT devices
- Planned in 1.7: Devices that publish over MQTT: Flexway will take them in through its MQTT listener, with an identity and a quota per device.
- Rate and quota per caller
- A token bucket per caller limits its rate; beyond it: 429 with Retry-After and the RateLimit headers.
- Publishing under contract
- Flexway publishes on your broker, under an AsyncAPI contract and in a CloudEvents envelope, what it receives over HTTP.
- Signed webhooks
- Flexway delivers your events to your partners as signed, replayable webhooks.
- Real-time streams
- Real-time streams (SSE, WebSocket) are relayed without holding back; identity and rate are checked when they open.
- Sensitive request pinned
- A request marked sensitive goes only to an internal model, never to an external provider.
- MQTT broker
- Your Kafka, AMQP, MQTT and NATS brokers: Flexway publishes on them under an AsyncAPI contract, in a CloudEvents envelope.
- Irrigation services
- Your REST and gRPC services: they receive only the requests Flexway let through, under deadline and circuit breaker.
- Internal model
- A model running on your premises: sensitive requests never leave your infrastructure.
- Partner systems
- Your partners' systems: they receive your events as signed, replayable webhooks.
- Line: one route
- Interchange: shared decision
- Request
- Event
- Model or tool call
- Refusal
- Your infrastructure
- Planned
- Rate and quota per callertokens, quota per tenant
- Publishing under contractHTTP to MQTT, CloudEvents
- Signed webhooksonly the tenant's events
- Real-time streamsSSE, WebSocket, unbuffered
- Sensitive request pinnedalways to an internal model
1An irrigation recommendation, reviewed before acting
What Flexway decidesThe assistant's request, marked sensitive, is pinned to your internal model, within the farm's budget.
What is protectedField data does not leave for an external model; the farmer approves, and only the local controller drives the valves.
2A partner receives only what concerns it
What Flexway decidesFrom the broker, signed, replayable webhooks: the subscriber receives only its tenant's events.
What is protectedThe partner has no access to the broker nor to other farms' data.
3An advisor follows sensors live
What Flexway decidesThe SSE or WebSocket stream is relayed unbuffered from the broker, under the same identity decision.
What is protectedThe browser never talks to the broker; it sees only its tenant's channels.
Farm apps
The applications that call your APIs: each request goes through Flexway, which checks the contract and the identity before reaching your systems.
Routes through here
Agronomy assistant
An AI assistant: it calls the models through Flexway's OpenAI-compatible surface, under budget and policy routing.
Routes through here
Broker events
A broker whose messages Flexway consumes to deliver them to your partners as signed webhooks.
Routes through here
MQTT devices
Planned in 1.7: Devices that publish over MQTT: Flexway will take them in through its MQTT listener, with an identity and a quota per device.
Rate and quota per caller
A token bucket per caller limits its rate; beyond it: 429 with Retry-After and the RateLimit headers.
- Decision
- tokens, quota per tenant
- Catalogue features
- Rate per caller (token bucket) ; 429 with Retry-After and RateLimit headers ; Quota per tenant per day and month
Routes through here
Publishing under contract
Flexway publishes on your broker, under an AsyncAPI contract and in a CloudEvents envelope, what it receives over HTTP.
- Decision
- HTTP to MQTT, CloudEvents
- Catalogue features
- AsyncAPI as the source of the asynchronous plane ; Mediation of the synchronous to asynchronous boundary ; AMQP(S) and MQTT
Routes through here
Signed webhooks
Flexway delivers your events to your partners as signed, replayable webhooks.
- Decision
- only the tenant's events
- Catalogue features
- Signed, replayable outgoing webhooks
Routes through here
Real-time streams
Real-time streams (SSE, WebSocket) are relayed without holding back; identity and rate are checked when they open.
- Decision
- SSE, WebSocket, unbuffered
- Catalogue features
- Streams relayed without holding: SSE and chunked bodies ; WebSocket relayed ; AMQP(S) and MQTT
Routes through here
Sensitive request pinned
A request marked sensitive goes only to an internal model, never to an external provider.
- Decision
- always to an internal model
- Catalogue features
- Sensitive requests pinned, sovereignty and fallback by policy ; Budget and rate per tenant
Routes through here
MQTT broker
Your Kafka, AMQP, MQTT and NATS brokers: Flexway publishes on them under an AsyncAPI contract, in a CloudEvents envelope.
- Catalogue features
- AMQP(S) and MQTT
Routes through here
Irrigation services
Your REST and gRPC services: they receive only the requests Flexway let through, under deadline and circuit breaker.
Routes through here
Internal model
A model running on your premises: sensitive requests never leave your infrastructure.
Routes through here
Partner systems
Your partners' systems: they receive your events as signed, replayable webhooks.
- Catalogue features
- Signed, replayable outgoing webhooks
Routes through here
What the sector requires
- MQTT · AsyncAPIDeclared sensor channels, not open topics
- A channel exists only if the contract declares it; an application publishes over HTTP, the gateway publishes to your broker in a CloudEvents envelope. Field telemetry reaches it through your own field gateway.
- Cooperatives, partnersEach farm keeps its data
- One identity per farm (API key or certificate bound to a tenant); a subscriber receives only its tenant's messages; signed, replayable webhooks to partners, quota per tenant.
- RecommendationsAgronomic recommendations within budget
- OpenAI-compatible inference with a budget per tenant; a sensitive request stays on your internal model, never sent to an external one; the audit keeps metadata, never the prompt.
- SupervisionSensors followed live
- An advisor's dashboard consumes a stream over SSE or WebSocket without speaking MQTT, relayed unbuffered; end-to-end traces.
What the sector expects
The expectations of your sector found in the market analysis, and where Flexway stands on each; what another component does better is stated.
| What enterprises expect | Flexway v1.6.3 |
|---|---|
Irrigation, machines: AI loop -> physical commandCommand authorised by scope (1.7.0); condition on the real state: candidate; physical safety systems stay independent | Partly · next to be scheduled |
| Coordination between farms and servicesCross-organisation exchange with a declared purpose: candidate | To be scheduled |
| Autonomous local orchestrationLocal decision by declared rules; orchestration stays with the decision service | Partly · next to be scheduled |
| Coordination between actorsMultiple issuers, partner mTLS, token exchange, per-field encryption; declared purpose of use: candidate | To be scheduled |
| Safety of autonomous machinesCommands under scope; the emergency stop stays independent and takes precedence | Partly · next in 1.7 |
Upcoming releases are not commitments; "Delivered" only when the catalogue of the published release says so.
How Flexway answers
Declared sensor channels, not open topics
- AsyncAPI as the source of the asynchronous planeDelivered · v1.5.0
- AMQP(S) and MQTTDelivered · v1.5.0
- Mediation of the synchronous to asynchronous boundaryDelivered · v1.5.0
Each farm keeps its data
- Signed, replayable outgoing webhooksDelivered · v1.5.0
- API keys and client mTLS as first-class identitiesDelivered · v0.1.0
- Quota per tenant per day and monthDelivered · v0.1.0
Agronomic recommendations within budget
- Budget and rate per tenantDelivered · v0.1.0
- Sensitive requests pinned, sovereignty and fallback by policyDelivered · v0.1.0
- Metadata audit, never a promptDelivered · v0.1.0
Sensors followed live
- Streams relayed without holding: SSE and chunked bodiesDelivered · v0.1.0
- WebSocket relayedDelivered · v0.1.0
- W3C traces propagated end to endDelivered · v0.1.0
State in Flexway's latest published release; a feature is marked delivered only with its release.
What Flexway does not do
- Flexway is not a field gateway: it speaks neither Modbus, OPC UA, CoAP nor Bluetooth, and translates no equipment protocol. Sensors and controllers reach your broker through your own field gateway.
- Connecting devices directly over MQTT, with one identity per device, is not in the published release: it is planned for an upcoming one.
- No offline operation on the farm: Flexway does not buffer, on the farm, the measurements taken while the network is down; that belongs to the field gateway.
- Flexway drives neither valves nor machines and does not ensure their safety: critical functions stay in dedicated controllers. The gateway is one control point, never the only safety mechanism.
- Flexway provides neither the decision models (irrigation, crops, livestock) nor the management of sharing consents: it enforces the rules your services declare. It is never a broker: it relies on yours.
Let's talk about your gateway
Flexwiz is a young company: you talk directly with the person who founds it. Tell us what you want to run through Flexway. We talk about your infrastructure and your digital sovereignty requirements.
Online booking is coming soon; until then, an e-mail is enough.