Early product

Metoriq

Metadata-driven data integration, executed on the server.

Metoriq is being built to help technical teams define, govern, and run data integrations with clarity, traceability, and control.

Follow the launch Understand the proposal 
$ metoriq setup status
status: initialized

$ metoriq tenants list
acme  ACME Corporation  active

$ metoriq connect acme admin@acme.com
SHOW ENVIRONMENTS;
CREATE ENVIRONMENT KEY dev PROPERTIES JSON `{ "name": "Development" }`;
DETAIL ENVIRONMENT KEY dev;
GENERATE ALTER ENVIRONMENT KEY dev;
DISABLE ENVIRONMENT KEY dev;
ENABLE ENVIRONMENT KEY dev;
Sources ERP · Databases · Files · Storages · APIs
Metadata Catalog Metoriq Runtime Governed execution workspace
Outputs RAW · Databases · Storages · APIs · Flows

What is Metoriq?

Metoriq is a server-side platform for defining, executing, and governing data integrations from metadata. Instead of treating integrations as scattered scripts or isolated jobs, Metoriq organizes connections, environments, models, flows, variables, executions, and history as governed metadata.

CLI, scripts, and the future VS Code extension act as authoring, validation, administration, and monitoring interfaces, while the Metoriq runtime centralizes execution, logs, auditability, and flow evolution.

Benefits

More governable integrations

Centralize connections, environments, models, and executions in a metadata catalog, reducing scattered integrations that are hard to maintain.

Server-side execution

Integrations run on the server, not on the user's machine, opening the path for logs, audit, permissions, scheduling, and controlled execution.

PostgreSQL workspace

PostgreSQL acts as the initial metadata foundation and execution workspace for RAW, staging, and SQL transformations.

Extensible connectors

The core is designed for connectors by contracts and plugins, without coupling the platform to a single source or destination.

Built for teams and environments

Tenants, environments, and workspace profiles are part of the design from the beginning, supporting DEV, QA, and PROD separation.

Traceable by design

Models, commands, runs, and history can evolve toward documentation, lineage, and audit trails generated from the same metadata foundation.

Available soon

Metoriq is in active development. The current foundation already covers setup, the internal metadata database, tenants, environments, protected TenantAdmin, an initial CLI, and basic MCL commands.

Next steps include connector contracts, execution workspace, data movement, transformations, and the first real integration flows.

We are building Metoriq incrementally, with small milestones, continuous technical validation, and focus on a solid architecture before broad commercial availability.

Development notes

Metoriq is being built through small technical milestones. These public notes summarize the architecture and current progress for people who want to follow the product as it evolves.

Open note

Architecture overview

Target architecture, principles, and product direction.

 Open note

Milestone 000 — Foundation

Initial .NET solution, project boundaries, health checks, CLI base, and tests.

 Open note

Milestone 001 — Setup / Bootstrap

Official installation bootstrap, metadata database initialization, setup status, and migrations.

 Open note

Milestone 002 — Metadata Core

Initial metadata catalog with tenants, environments, TenantAdmin, MCL, models, and connections.