Deploy

Our cloud, your instance, or the server next to the line.

The same platform in every case. The whole stack idles in about a gigabyte of memory, so it runs where your data is.

~1 GB
idle RAM, everything included
Shared cloud

Start today

Go to the platform and connect a device. Your data lives in its own schema.

Go to platform
Dedicated

Your own instance

Run by us, on its own servers, with your domain and your brand.

Contact us
Your server

On-premise or edge

Docker on hardware you control — a data centre or a small box in the plant.

Contact us
Option Shared cloud Dedicated Your server
Run byKowisteKowisteYou
Data locationKowiste regionA region you chooseWherever the server is
IsolationSchema per organization and branchOwn instanceOwn hardware
Your brand and domain—IncludedIncluded
Start Go to platform Contact us Contact us
What runs

The whole platform, not a piece of it

One compose file starts everything the platform needs. The only outside services are the ones you configure, such as email delivery.

PostgreSQL + TimescaleDBdata and time series
Message brokerMQTT for devices, internal stream
Workflow engineschedules, reports, retries
Sign-in serviceusers, sessions, invitations
BackendAPI, ingest, evaluation
Web app and admin appwhat your people use
Monitoringlogs, metrics, request traces
Install

Three commands

Fill in the environment file, create the schemas, start the stack. Migrations run on every start, so an update is a new image and a restart.

# 1 · configure
cp .env.example .env

# 2 · create the schemas
make migrate

# 3 · start everything
docker compose up -d
Hardened by default

Safe to put on the plant network

Read-only containers

No capabilities, no privilege escalation, a non-root user, memory and CPU limits.

Isolation in the database

Each organization and branch in its own schema; the application role owns them.

Device access on the broker

Device logins are checked on every connection; commands only reach your own devices.

No calls inward

Webhooks can't reach private addresses, so an action can't be pointed at your network.

Metrics stay private

Prometheus metrics on a separate local listener, never on the public API.

Every request traced

SQL, sign-in and permission checks per request, without passwords or addresses in the logs.

Your brand

Offer it as your own

On a dedicated instance or your own server, put your logo, colours and domain on the apps. Each of your customers is an organization, with its own branches, users and plan limits.

Tell us where it needs to run.

Next: compare the plans →