Documentation
Altius Pipeline Builder
Compose data pipelines on a canvas, validate schemas at every stage, and keep lineage and semantic context attached from source to decision. This documentation describes what ships in the repository today.
Architecture
All client traffic enters through the API gateway. The gateway authenticates every request, enforces role-based access, and proxies to downstream microservices. Business logic lives in the services — not in the gateway.
API Gateway
:4000Single entrypoint — JWT auth, RBAC, rate limiting, and routing to all services.
Schema Engine
:4001Schema registry, real-time validation, compatibility checks, and ontology CRUD.
Sandbox Manager
:4002Isolated workspaces with propose, review, merge, and revert lifecycle.
Pipeline Core
:4003DAG validation, execution, schedules, event streams, and node catalog.
Governance Dashboard
:4004Pipelines, projects, audit log, RBAC, lineage, entitlements (proxied via gateway).
Connector Framework
:4005Connector type catalog and connection tests (proxied via gateway).
Key concepts
Pipelines
Visual DAGs composed on the canvas. Graph state lives in governance-dashboard; execution runs through pipeline-core.
Schemas
Registered contracts in schema-engine. Nodes validate payloads in real time; drift is surfaced before merge.
Validation
POST /schema/validate checks payloads against registry versions. Pipeline validate runs graph and binding checks.
Ontology
Object types, link types, and entity instances provide semantic context that travels with pipeline data.
Governance
Audit log, RBAC policies, lineage, checkpoints, and sandbox approvals keep changes reviewable.
Getting started
- Environment. Copy
.envfrom the repo root. Start Postgres and Redis, runalembic upgrade headin schema-engine, then start services (gateway on port 4000). - Sign in. Open /login. In development, any email with password
devpasswordworks when the database is configured. - Build. Open /app/pipelines to create and edit pipelines on the canvas.