Resilient Infrastructure
for autonomous systems
Intuitive infrastructure to deploy autonomous systems in mission-critical production. Think Kubernetes for autonomy.
Trusted by major public safety and defense institutions
The autonomy layer your
hardware runs on
Edge SDK on every device. Mesh networking between nodes. Telemetry pipelines to your infrastructure. All orchestrated.
Edge-native compute
SDK runs on the device. Adapters normalize hardware. Platform handles routing, not your code.
Mesh-grade networking
Peer-to-peer between hardware, uplink to your infrastructure. Disconnection-tolerant by design.
Deploy on your terms
EU cloud, on-premise rack, or fully air-gapped. Same containers, same config, your compliance.
Speak your stack.
We handle the rest.
Up and running in five steps
Install the SDK, configure your connection, and start calling services. The platform handles orchestration, communication, and routing.
Start the platform
Spin up all platform services locally with Docker. One command — the framework handles orchestration, networking, and service discovery.
docker compose up -d
Install the SDK
Add the Zequent SDK to your project. Pick the Client SDK for backend applications or the Edge SDK for hardware adapters.
<dependency>
<groupId>com.zqnt.sdk</groupId>
<artifactId>client-sdk</artifactId>
<version>1.0.0</version>
</dependency>Configure your connection
Point the SDK at your platform services. Works the same way locally, in Docker Compose, and in Kubernetes.
# Docker Compose — use service names
REMOTE_CONTROL_SERVICE_HOST=remote-control-service
MISSION_AUTONOMY_SERVICE_HOST=mission-autonomy-service
LIVE_DATA_SERVICE_HOST=live-data-service# Kubernetes — enable service discovery
REMOTE_CONTROL_SERVICE_USE_STORK=true
REMOTE_CONTROL_SERVICE_STORK_NAME=remote-control-service
REMOTE_CONTROL_SERVICE_USE_PLAINTEXT=falseREMOTE_CONTROL_SERVICE_HOST=localhost
REMOTE_CONTROL_SERVICE_PORT=8002
MISSION_AUTONOMY_SERVICE_HOST=localhost
MISSION_AUTONOMY_SERVICE_PORT=8004
LIVE_DATA_SERVICE_HOST=localhost
LIVE_DATA_SERVICE_PORT=8003Write your first command
Inject the client and call typed methods. The SDK handles connections, serialization, retries, and circuit breaking.
@Inject
ZequentClient client;
public CompletableFuture<TakeoffResponse> takeoff() {
return client.remoteControl().takeoff(
TakeoffRequest.builder()
.sn("DEVICE_SN")
.latitude(47.3769f)
.longitude(8.5417f)
.altitude(100.0f)
.build()
);
}Run it
Start your application and hit the endpoint. Your code talks to the platform — done.
mvn quarkus:dev
# Test your endpoint
curl -X POST http://localhost:8080/drone/takeoff
Everything autonomous systems need
From direct hardware control to fleet-wide intelligence. Each capability is a service in the platform, accessible through the SDK with typed interfaces and structured responses.
Remote Control
Direct command execution for flight control, gimbal positioning, and manual input. Low-latency command-response architecture ensures responsive operation regardless of distance.
Live Telemetry
Persistent data streams for position, battery, signal, and custom sensor data. Push from the edge, subscribe from the application -- real-time visibility across your entire fleet.
Mission Planning
Define missions with tasks, waypoints, and scheduling. The platform handles execution order, state transitions, and progress tracking across concurrent operations.
Data Streaming
Live video feeds from cameras and sensors on the edge. Multi-stream support, recording, and relay -- all routed through the platform with no direct device access required.
Asset Management
Registry for all connected hardware -- drones, docks, vehicles, sensors. Manage organizations, capabilities, and metadata. The single source of truth for your deployment.
Detection and AI
Computer vision and inference pipelines at the edge or in the cloud. Object detection, tracking, and classification with pluggable model backends integrated into the data flow.
From zero to production in three steps
Get operational fast. The framework handles infrastructure so you focus on your application logic and hardware integration.
Add the SDK
Add one dependency to your project. The SDK auto-configures connections to platform services using environment variables. No boilerplate, no scaffolding tools required.
Connect your hardware
Build an edge adapter for your specific device by implementing a single interface. Override the methods your hardware supports -- the framework handles registration, streaming, and routing.
Ship to production
Deploy to EU cloud or on-premise with the same codebase. Docker containers, environment configuration, and compliance are built into the deployment model from day one.
Built for real-world operations
Defense, public safety, agriculture, industrial inspection -- the leading companies rely on Zequent for running autonomous systems in mission-critical production.
From prototype to production. Same platform, any scale.
What you actually get
Technical decisions that make a difference when you are shipping autonomous systems to production environments.
No glue code
The framework defines clean interfaces between your application and the hardware layer. Add a dependency, call typed methods -- no custom protocols or serialization layers in between.
Hardware-agnostic
Switching vendors means writing a new adapter, not rewriting your application. The framework abstracts hardware operations so your application logic stays the same regardless of the hardware underneath.
Deploy anywhere
EU cloud or fully air-gapped on-premise. Same containers, same configuration, same SDKs. Your application code does not change between deployment targets. GDPR compliance is built into the architecture.
Production-grade scale
Services scale independently. Sustained telemetry from hundreds of assets, concurrent mission operations with conflict detection. This is framework infrastructure for real deployments, not a prototype toolkit.
Open, not opaque
You see the interfaces. You see the data models. You control the adapter code. No proprietary black boxes between your application and your hardware. The framework provides structure. The logic is yours.
Modern stack
Built on a modern, battle-tested runtime optimized for fast startup, low memory footprint, and native compilation. The same stack that runs cloud microservices at scale, applied to robotics.
Source code on GitHub
The SDKs are distributed as packages through GitHub Packages. The source is fully public — browse the code, report bugs, or contribute.
Client Java SDK
zqnt-client-sdk-java
Add as a dependency — connect to Zequent services from your application.
Edge Java SDK
zqnt-edge-sdk-java
Add as a dependency for the edge side — runs on device, syncs with the platform.
Utils
zqnt-utils
Shared data models, serialization, and config primitives used across SDKs.
Documentation
zequent-framework-docs
Zequent ecosystem documentation. Learn how to use Zequent, from SDK setup to advanced features.
Contact
Let's build something together
office@zequent.com
Phone
+41 (0) 762087620
Office
Chüngstrasse 31, 8424 Embrach, ZH, Switzerland
Zequent Technologies