eltPulse is the hosted control plane for defining ingestion pipelines, keeping definitions in your workspace, and exporting runnable artifacts into repositories you control. These guides mirror how we structure product docs on ServicePulse — scannable sections, public URLs, and room to grow.
Getting started
Sign in, create your first pipeline, export artifacts.
Concepts
Pipelines, runs, connections, monitors, gateways — and how to route work to a specific gateway.
Pipelines
Sources, destinations, canvas, generated code, and workspace manifests.
AI Builder
Natural-language pipeline generation with dbt and workspace project linking.
Catalog & assets
Authenticated browse, metadata tags, and team RBAC roles.
Runs
Structured logs, telemetry (rows/bytes/progress), PATCH contract for gateway and app.
Orchestration
What runs vs when: schedules, eltPulse sensors, and portable exports for other orchestrators.
Gateway
Self-hosted connector: tokens, env vars, /api/agent/* contract, Docker and cloud runtimes.
Integrations
Managed GitHub org, optional BYO OAuth, future connectors.
Repositories
How customer repos fit under the eltpulse/ layout.
Security & data
Auth, secrets, and what we store in Neon.