Streams, tables and documents come in as they happen. You define the ontology. Everything becomes an object you can query, share and act on.
Sources
Data arrives from everywhere.
Sensor streams, operational tables, documents. Here: aircraft, vessels, vehicles and drones over Gothenburg, landing as they happen.
Objects
Every observation resolves to an object.
Identity, state and relations, always current.
Ontology
Objects live in your ontology.
You define the object types, their fields and how they relate. Streams hang off object types, holding each object’s records as they arrive.
From signal to decision, in real time.
A sovereign data platform for streams, tables and documents. Built in Europe.
Scroll
Projects
Built from what you already have.
Connect any source, streaming or batch. Pipelines live in projects, with ownership, lineage and access control at the boundary.
Ontology
Your ontology, kept in sync.
Tables are mapped to the object types you defined. The sync runs on every commit, so every object reflects the data beneath it.
Agents
Three ways to put agents to work.
Analyst agent
Query the ontology. Render the answer.
Data engineering agent
Notebooks and flows, on request.
Operations agent
Respond to operational change.
Arawise · Gothenburg · Europe
Your most critical data, yours to use.
A European sovereign data platform for storing, transforming, analysing and sharing sensitive information, with an ontology you define and the platform keeps current.
Questions
Frequently asked questions
01What is Arawise?
Arawise is a European data platform for organisations that work with sensitive data. Streams, tables and documents land in projects, you define an ontology of object types over them, and people and AI agents work on that model: SQL, notebooks, charts, alerts and automations, all under project-level access control. It is built on open standards such as Apache Iceberg, Trino and Kafka-compatible topics.
02What is an ontology in a data platform?
An ontology is a model of the things your organisation runs: object types such as Vessel, Berth or Aircraft, their fields, and the relations between them. Instead of asking analysts to rediscover the same joins in every query, the ontology captures them once. In Arawise you define the ontology yourself and the platform keeps it in sync with the tables underneath.
03How does Arawise keep the ontology in sync with source data?
Each object type is mapped to tables in the lake: one table establishes which objects exist, and further sources and joins fill in fields. The sync runs whenever a mapped table receives a commit, so objects reflect the latest data without a separate pipeline to maintain.
04Does Arawise support real-time streaming data?
Yes. Topics carry streaming data into a project, transforms shape it with streaming SQL, and alerts fire on records as they arrive. A stream can also be declared on an object type, so each object keeps its own record history, for example every position report for a vessel.
05What is a project in Arawise?
A project is the bounded unit for data and work. It has its own storage, its own SQL schema and its own access roles. Sources land in projects, flows and notebooks run in projects, and access is decided at the project boundary.
06Can AI agents query the ontology?
Agents scoped to a project can answer questions over its data and the ontology, render tables and charts, and read documents. A project assistant can draft notebooks, transforms and alerts on request. A person reviews and approves before anything is created.
07Where is my data stored and who can see it?
Arawise is multi-tenant with a physically separated data plane for every tenant, hosted in Europe. Within a tenant, access is granted per project and per object type, and data markings follow records into every read, including reads by agents.