Recent Executions
Unified history across engines, shown as business stages.
Source: Ardana control-plane snapshot · loading live data
Data Quality
Operationally important scores only.
Attention Required
Failures, drift, and stewardship work.
Upcoming Schedules
Late data and continuous jobs are visible.
Create
Create a data solution
Start from business use cases, not an empty engine canvas.
Build
Apache Hop Web
Design and maintain data pipelines in the embedded Apache Hop workspace. Advanced Ardana designer tools are available when enabled by configuration.
Designer ready. Select a node or add a component.
Pipelines
Workflows
SQL Models
APIs
Default Build experience
Embedded Apache Hop Web
Use native Hop editing directly from the Build page with the current Ardana session and platform proxy controls.
Checking Hop Web configuration…
Publish saved pipeline
Copy a saved pipeline from your private Hop Web session to the controlled project area for approval.
Hop Web workspace
No pipeline selected.
Connect
Unified connection manager
Create, test, discover, and assign governed logical connections for pipeline development and operations.
Connections
Select a connection to inspect usage, environments, and schema.
Connection details
Choose a connection from the list.
Connection builder
Credentials remain server-side environment-secret references and are never returned as values.
Save the connection, select it, then run a real test.
Discovered schema
Build
CDC
Continuously capture source changes into a governed destination. Workflow: Source → Tables → Initial data → Destination → Review.
Loading CDC readiness…
CDC readiness
Checks that run before a CDC definition can be deployed.
Source privileges
Replication or log access on every selected table, with safe per-source DBA instructions when access is missing.
Governed destination
A database, warehouse, object-store, or governed Kafka stream connection.
Connector support
Checking the reviewed SeaTunnel connector capability registry…
Runtime
Checking the SeaTunnel Zeta runtime…
Deployment approval
Deployments enter the normal approval and audit workflow before a job starts.
CDC streams
Deployed streams show lifecycle state, lag, throughput, and snapshot progress.
Loading CDC streams…
Build
Data Transfers
Full load, replication, incremental movement, and batch sync between governed connections. Workflow: Source → Destination → Mode → Options → Review.
Loading transfer runtime…
New data transfer
Governed source and destination connections only. Credentials resolve server-side and never reach the browser.
Transfers
Each transfer shows source, destination, mode, and runtime state. Operate actions respect workspace roles.
| Name | Source | Destination | Mode | Status | Actions |
|---|
No transfers are defined yet. Use New transfer to connect a governed source and destination.
Transfer detail
Lifecycle state, checkpoint, and sanitized diagnostics.
Loading transfer status…
Build
Data Models
SQL transformations, dimensions, facts, marts, and warehouse tests executed by a version-pinned dbt runner. The browser never receives database credentials or profiles.yml values.
Loading dbt runner state…
dbt project
A Git-backed project and working branch; credentials resolve server-side and are never submitted by the browser.
No project revision is pinned yet. Discover a branch to list its models, sources, and tests at an immutable commit.
Models
Model list with layer and latest run state from the pinned revision. Select a model for detail, graph, SQL, tests, and history.
| Model | Layer | Path |
|---|
No models are listed yet.
Run controls
Every action maps to one governed dbt Core command on the pinned revision and records immutable evidence.
Run history
Immutable execution evidence: commit, versions, selector, artifacts, and terminal result.
| Run | Command | Status | Commit | Artifacts | Finished |
|---|
No dbt runs are recorded yet.
Model detail
Graph, SQL, tests, documentation, and per-model history come from ingested manifest and run-results artifacts.
Select a model from the list to see its graph, SQL, tests, documentation, and run history.
Operate
Orchestration
Schedules, dependencies, retries, and release promotion for finite work.
Batch lane
Airflow finite workflow controls
Trigger, refresh, inspect, and correlate scheduled or ad-hoc Hop pipeline runs.
Schedules and SLA
Configured release-backed batch schedules with cadence, next run, and lifecycle controls. Next run is computed from the cron expression in the declared timezone.
| Schedule | Cadence | Next run | State | Actions |
|---|
Hop approval to production
Prioritized release queue for native Apache Hop .hpl artifacts. Full file discovery is kept behind a compact review list.
Promotion and rollback evidence
Promotion moves an approved release across environments; rollback re-fetches a prior immutable digest. Evidence comes from recorded release promotions only.
Operate
Runs
Batch, transfer, and model execution history with CI/CD pipeline visibility and controls.
Execution history
Runs returned by the control-plane snapshot. Search and filters round-trip through the URL and reset pagination-free lists cleanly.
| Workload | Type | Started | Duration | Status | Trigger |
|---|
Runs load from the control-plane snapshot after sign-in.
Governed Git workflow
CI/CD execution visibility and controls
GitLab pipelines, deployment evidence, manual jobs, retry/cancel controls, and Airflow evidence correlation.
GitLab configuration
Pipelines
Job controls
Deployments and evidence
Unified execution timeline
Batch executions and streaming service events in one operational chronology.
Release queue
Govern-ready Hop releases
Releases awaiting approval or in promotion. Maker-checker approvals, deploys, promotions, and rollbacks are performed on the Orchestration queue with recorded evidence.
Operate
Monitoring
Continuous stream health, incidents, and engine diagnostics.
Continuous streams
Live state returned by the control plane for registered streaming services. Lifecycle controls stay in the stream lane below; lag and message times are observed values only.
| Stream | State | Lag | Replicas | Last message |
|---|
Stream lane
Hop streaming service controls
Start, stop, restart, and monitor continuous Hop services independently from Airflow DAG runs.
Incidents and attention queue
Failures, degraded streams, unhealthy datasets, and inactive schedules that need an operator decision.
Selected detail panel
Context for the most urgent execution, service, schedule, or health item.
Engine and backend diagnostics
Airflow, platform API, release workflow, and service-registry checks. Engine-native diagnostics stay role-authorized and out of the primary navigation.
Operate
Data Quality
Warehouse tests, freshness, reconciliation, and quality results.
Quality rules
Rules returned by the control-plane snapshot with their last recorded outcome. Row-level results and history arrive with the dbt and OpenMetadata result publishers.
| Rule | Dataset | Kind | Severity | Last outcome |
|---|
Rule detail
Context for the selected rule from live control-plane data. No rule outcomes are inferred when a result source is not connected.
Govern
Catalog
Governed metadata, discovery, and schema evolution.
Dataset catalog
Datasets returned by the control-plane snapshot with ownership and quality state.
| Dataset | Layer | Owner | Quality |
|---|
Dataset detail
Ownership, layer, project, and quality state for the selected dataset. Column-level schema history arrives with the OpenMetadata sync, which is not connected yet.
Govern
Lineage
Technical lineage, impact analysis, and execution provenance.
Lineage edges
Source-to-target edges returned by the control plane. Search matches either endpoint; direction filters relative to the match. Execution provenance per edge arrives with the lineage publisher.
| From | Operation | To |
|---|
Govern
Environments
Environment-scoped runtime policy and targets.
Environment workloads
Projects and recorded runs grouped by the environment field returned by the control plane. Readiness is never inferred from the group name.
| Environment | Projects | Recorded runs | Schedules |
|---|
Promotion policy
Applied by the control-plane release flow, not by this page.
UAT → PROD promotion requires an approved release and a release-approver, data-owner, or platform-admin role.
Definitions and variable schema promote; resolved environment values and secret values never do.
Rollback restores a prior immutable SHA-256 digest and does not rewrite artifact history.
Secrets isolation
Environment isolation rules the platform enforces at the secret boundary.
Production secrets never fall back to UAT or DEV values; a missing required secret is a configuration error.
Manage references under Govern → Secrets once the vault backend is connected.
Runtime policy editing is not connected yet; environment policy ships with the configuration repository route.
Govern
Variables
Non-sensitive configuration values with Global → Tenant → Project → Environment inheritance. Secrets never live here.
Variable management is not connected to the configuration repository yet. Non-sensitive platform values currently ship with the Compose environment template; effective-value inheritance is shown per variable once the route ships.
Variables
Target structure: lower scopes override higher scopes (Global → Tenant → Project → Environment), the resolved-from scope is always named, and promotions carry definitions, never resolved values.
| Key | Effective value | Resolved from | Overrides |
|---|
No variables are defined yet. Rows appear here with inheritance-accurate effective values once the configuration repository route is connected.
Govern
Secrets
Masked secret management, rotation, and access policy. Values are never shown by default in any list or audit view.
Secret management is not connected to a vault backend yet. Credentials remain server-side environment-secret references on connections and are never returned as values.
Secrets
Target structure: references are masked in every list and audit view, per-environment isolation is enforced (PROD never falls back to UAT or DEV), and rotation and access counts are shown without exposing values.
| Secret reference | Environment | Used by | Last rotation |
|---|
No vault-backed secrets are registered yet. References, rotation posture, and access policy appear here once the vault backend route is connected.
Govern
Access Policies
Identity, role, and workspace-scoped access controls with least-privilege defaults.
Access policy administration is not exposed yet. Identity and roles are managed in Keycloak, user and role administration lives under Admin → Users & Roles, and workspace claims already scope platform APIs.
Role and workspace matrix
Target structure: effective permissions per role and workspace once policy administration ships. Separation of duties (approver ≠ submitter) is enforced server-side.
| Role | Workspace scope | Key permissions | Members |
|---|
The role and workspace matrix appears here when access policy administration is connected.
Policy rules
Target structure: explicit allow rules for destinations, secrets, and environments, with least-privilege review dates.
| Workspace | Members | Admins | Review due |
|---|
No policy rules are defined yet. Workspace access rows with review dates appear here once policy administration is connected.
Admin
Users & Roles
Admin-managed user and role administration. Restricted to platform-admin and security-admin roles, with backend audit logging.
Checking admin permissions…
Managed users
List, filter, update, and deactivate users through the control-plane admin API.
Invite / create user
Least-privilege defaults. Privileged admin grants stay out of this path.
Ready to create a least-privilege user.
Admin API limitations
Admin
Engines
Runtime, connector, and engine-native diagnostics.
Workers
Admin
System Settings
Platform configuration and readiness.
Platform readiness
Operational capabilities available in the Ardana workspace.
Admin
Audit Logs
Immutable audit events for configuration, release, and secret actions.
Audit logs
Admin
Subscription license
Enter the vendor license key to activate subscription entitlements. The control plane verifies the key locally and stays the sole entitlement decision point.
Loading license status…
License status
Verified locally by the control plane on every status check. The raw key is never displayed again after saving.
Enter license key
Paste the key exactly as issued. Saving verifies the signature and expiry before storing.