Every analyst. Every engineer. One canvas. Self-hosted visual ETL and data integration platform

Get your whole team building data pipelines, right in the browser. Analysts stop waiting on tickets, engineers stop rebuilding their work, and leaders trust the data again.

Start your 30-day trial Book a walkthrough

orders · nightly refresh Unsaved Draft Staging v7 Production v7 Succeeded

Postgres

Input

482,910 rows

CSV Files

Input

12,480 rows

Filter

Preparation

311,204 rows

Data Cleanse

Preparation

12,480 rows

Join

309,877 rows

S3 File

Output

309,877 rows

Data Out Messages Metadata Join · no run neededJoin · 50-row sampleProduction v7

order_idInt64

placed_atTimestamp

customerUtf8

amountDecimal128

regionUtf8

is_priorityBoolean

order_id	customer	region	amount
1043	Redwood Labs	West	1,284.00
1044	Bellhaven Co	North	312.50
1045	Orchard Group	West	9,940.10
1046	Kestrel Freight	South	2,410.00

02:00Started on Production v7
02:01Postgres read 482,910 rows
02:02Filter kept 311,204 of 482,910 rows
02:03Join matched 309,877 rows
02:04S3 File wrote 309,877 rows. Succeeded.

Why Trinium

Faster data onboarding, fewer fragile jobs, and numbers the business can trust.

Eight things Trinium changes for a data team.

Onboard new data without new code

One input reads a whole folder of partner files. Files whose columns moved, appeared or vanished are lined up by name, and rejected rows go back to the partner by email.

Partner file onboarding

Retire the jobs only one person understands

Scripts, cron entries, cloud functions and desktop workflows become pipelines the whole team can open, test and rerun. The migration guides map what you run today.

Retiring scripts and cron

Trust every number you hand over

Every node counts its rows on every run, validation rules send bad rows to an output of their own, and Data Compare shows each cell where two datasets disagree.

Reconciliation you can hand over

Let the people who need the data build it

Analysts build and test in a browser tab, with formulas in plain SQL. Engineers deploy that same pipeline, so nothing is rebuilt in a second tool.

How building works

Change pipelines without breaking production

Edit a draft, test it on 50 rows and deploy it to staging. Production runs only what went through staging.

How deploys work

Grow without growing the bill

Every account is free, a bigger machine never costs more, and both prices are published.

See pricing

Clear the security review

Trinium runs inside your network and sends us nothing. People sign in through your own provider, production is a permission of its own, and every change carries a name.

Security overview

Do on one server what usually needs a cluster

Large joins, sorts and summaries run on an ordinary server, with no cluster to stand up or tune.

See the measured run

Who it's for

Analysts build it. Engineers ship it. IT signs off.

Everyone works on the same pipeline, so the person who asked for a change can open it, test it and see exactly what it does.

Analysts & business teams

Build it yourself, without a ticket or a license to wait for.

A 50-row preview of every step, one click of Test away
Formulas in plain SQL, with [bracket] column names if you prefer them
Excel in, and formatted Excel reports and per-person emails out

The Monday report, off the desktop

Data engineers

Production pipelines without the glue code.

S3, Parquet and Iceberg, plus seven warehouses and query engines
Schedules, file-arrival triggers and Flows that branch on failure
Staging and production versions, with per-node telemetry on every run

Data-lake pipelines on S3 and Iceberg

IT, security & platform Single sign-on, directory sign-in, eight roles and an audit log of every change. Data leaders One platform for every role, a record of what every pipeline did last night and who changed it, and a bill set by servers rather than headcount. Data scientists Keep your model where you host it. API Lookup sends it each row and puts the answer back in the pipeline. Everyone else Results arrive as an Excel report, a Google Sheet or a Salesforce record.

The engine

100% Rust. No JVM. No garbage collector.

500,000,000rows, one server

80 node pipeline 8 vCPU, 32 GB of memory 33m 55s end to end

One measured run: half a billion rows read from a Parquet file on S3, sent through 75 steps of filters, formulas and column changes, then totalled and checked. Not one row was lost or duplicated, and more than 120 GB spilled to disk rather than running out of memory.

Many established visual ETL tools run on the Java virtual machine, which is why keeping one alive under load means heap flags, per-component memory settings and a lot of time reading stack traces. That is the standing cost of a garbage-collected data engine.

Trinium's engine is Rust from end to end, with no virtual machine to size and no collector to pause a run in the middle of the night. Every node runs at once, rows stream between them in batches, and the work that cannot stream spills to disk inside one memory budget instead of taking the process down.

Read how execution works

Built for production

The discipline engineers expect, on a canvas analysts can read.

Everything a pipeline needs once people depend on it: versions, schedules, orchestration, alerts and a record of every run.

A pipeline is a graph of steps. A Flow is a graph of pipelines.

Run pipelines in order or independently, branch on the outcome, and alert someone only when something fails.

Rolling back is one deploy, not an incident.

Every version is numbered and never changes, every deploy is recorded, and every run is stamped with the version it ran.

v7StagingProduction
v6Deploy
v5Deploy

Four ways a run starts.

Each one lands in the same queue, the same history and the same telemetry.

On demand
On a schedule
When a file lands
As a step in a Flow

Every run answers what happened.

Rows and time for every node, and peak memory and queue wait for every run.

Postgres482,910
Join309,877
S3 File309,877

One expression language, and it is SQL.

Filters, formulas and validation rules all share it, and [bracket] column names still work.

CASE WHEN [score] >= 90 THEN 'A'
     WHEN [score] >= 80 THEN 'B'
     ELSE 'C' END

Pricing

Priced per server. Everyone is included.

Pro counts one thing, the servers you run, and Enterprise covers as many as you need. Both prices are on the pricing page, with nothing to request.

Compare the editions

Noseat licensesEveryone in the company can have an account.

Noper-core licensesA 64-core box is still one server.

Nometered runsRun a pipeline every minute if you want to.

Nometered rowsVolume is a capacity question, not a billing one.

Nodes & connectors

The tools the job needs, already on the canvas.

On the way in: files, databases, warehouses, lakehouse tables and SaaS APIs. In the middle: cleansing, joins, parsing, reshaping, fuzzy matching, validation and reconciliation. On the way out: the same systems again, plus formatted Excel reports and email.

Everything listed ships in the product today.

Browse every node

Connects to

PostgreSQL

MySQL

SQL Server

MongoDB

Snowflake

BigQuery

Amazon Redshift

Databricks

ClickHouse

Trino / Starburst

Amazon Athena

Apache Iceberg

Amazon S3

Azure Blob Storage

Google Cloud Storage

SFTP

Network Share (SMB)

REST API

Google Sheets

Salesforce

HubSpot

Jira

Zendesk

SMTP (Email)

Self-hosted, properly

Your data never reaches us. Neither does your telemetry.

Read the security overview

Runs in your network. Trinium is a set of containers on your servers, beside a Postgres database you own, and nothing leaves except what your pipelines send. It ships no AI model and sends nothing to an AI service on its own.
Licenses verify offline. Your key is checked against a public key built into the binary, so there is no license server and no usage reporting.
Credentials stay encrypted. Secrets are encrypted at rest, and a pipeline holds only the name of a connection, never its password.
Nobody gets locked out. If a license lapses, new runs stop and everything else keeps working. Nothing is deleted.

Bring your hardest pipeline.

Rebuild one real pipeline of yours during the trial. It settles the question better than anything on this page.

Start your 30-day trial Book a walkthrough