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 Open MCL help

$ 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

Server-side execution
Metadata-driven
PostgreSQL workspace
Extensible connectors
Command line
Graphical interface
VS Code extension
CLI app

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.

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, metadata, tenants, environments, users, policies, schemas, connector types, connections, secrets, PostgreSQL READDATA/WRITEDATA/TRANSFORMATION paths, runtime logs, DATAFLOW runtime, ACTION runtime, TASK and FLOW, variables, fan-out, VERSION, message localization, SaaS entitlements, usage metering, license enforcement, SaaS provisioning, HTTP APIs, Web authentication/session foundations, permission-aware Web APIs, a productized Web server baseline, a real catalog Object Explorer, Web script execution, results/runs/diagnostics views, visual authoring, terminal workflows, local HML Docker packaging, managed script storage, file picker flows, managed storage exploration, and an environment dashboard workspace card.

Next steps include a human PostgreSQL authoring review, scheduling, retries, and distributed execution.

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

Public product documentation. Use this section to open the interactive MCL help.

Open MCL help MCL Command Help

Tree-style reference with syntax, descriptions, and examples for CLI and MCL commands.