What are we looking at?
Compare observed PostgreSQL schemas with your dbt catalog. Keep declared dependencies and imported run evidence close together.
SchemaModelResult
Development preview Built for data teams
When data breaks,
find your
way forward.
Understand what failed, what depends on it and what your team should review next. One evidence workspace for PostgreSQL, dbt and Airflow.
Free during preview. No card required.
Live workflow execution remains disabled.
More context. Clearer decisions.
A recovery plan your team can inspect.
A recovery plan your team can inspect.
YOUR NEXT INVESTIGATION, CONNECTEDIllustration · sample data
FlowSentraAnalytics workspace JDINCIDENT · SAMPLE-042
Needs investigationRevenue pipeline
Reported failurestg_ordersdbt model · error
Declared downstream1 modelPotential exposure
Recovery scope1 intervalExplicit boundaries
DECLARED DEPENDENCIESSnapshot evidence
POSTGRESQL SOURCEraw.ordersImported metadata
DBT MODELstg_ordersReported error
DBT MODELrevenueReported skipped
Prepare a reviewable next step
Review requiredExact task scope · declared writes · attached evidence
Evidence before actionExecution disabled
Keep the context with the decision.
From reported failure to an immutable review trail.
BEYOND THE RED STATUS
The failed task is
only the beginning.
The hard part is connecting the evidence. Bring the source, the dependency, the reported result and the proposed response into the same conversation.
What depends on this?
Trace potential downstream exposure from the run’s own snapshot. Make incomplete coverage and unobserved dependencies visible.
What can we review next?
Prepare a bounded recovery plan. Attach evidence, declare the intended outcomes and get an independent account to review the exact scope.
◇Plan → evidence → review
ONE CONNECTED WORKSPACE
Less tab archaeology.
More operational context.
Explore the platform, from understanding your data to preserving the reasoning behind a recovery decision.
CATALOG & LINEAGEA shared map of
A shared map of
your data landscape.
Import a PostgreSQL dbt manifest and discover permitted source schemas. Compare declared models with observed relations, without querying business rows.
- Versioned dbt catalog snapshots
- Declared dependency lineage
- Read-only schema and column discovery
- Explicit matched, unmatched and ambiguous results
DATASET CATALOGIllustration
analytics
orderswarehouse.raw.orders
Sourcestg_orderswarehouse.analytics.stg_orders
Modelrevenuewarehouse.analytics.revenue
Model Declared lineage, tied to a saved snapshot.
RUN EVIDENCE & INCIDENTSGive an incident
Give an incident
a useful starting point.
Inspect paired dbt run results, source freshness and saved Airflow observations. Attach investigation context to an incident and retain the evidence behind each update.
- Reported results and failure details
- Scheduled Airflow captures, grouped investigations and opt-in emails
- Freshness and schema-contract assessments
- Explicit incident ownership and lifecycle
INVESTIGATION CONTEXTIllustration
REPORTED DBT RESULTstg_orders · error
ReportedInspect the retained result details.
AIRFLOW OBSERVATIONExact task & interval
Compare saved evidence and coverage.
INCIDENT HISTORYKeep the investigation attached
Preserve context as the issue evolves.
A reported result is evidence, not a complete account of runtime behavior.
RECOVERY PLANNING & REVIEWMake the proposed
Make the proposed
response inspectable.
Define an exact interval and task scope. Declare code identity, logical write boundaries and expected postconditions, then preserve a version for independent review.
- Bounded static recovery simulations
- Customer-host read-only diagnostics
- Local artifact measurements with explicit provenance
- Immutable versions and separate-account review
CONTRACT REVIEWIllustration
◇
SAVED CONTRACT · VERSION 2Scope before action.
Recovery intervalExplicit · half-open
Task & attemptExactly bound
Local artifact reportOperator supplied
Independent decisionReview recorded
ACCESS & CONTROL-PLANE PROTECTIONKeep permissions
Keep permissions
and evidence in view.
Scope review access by project and environment. Preserve append-only decisions and make approval staleness visible when evidence, membership or access changes.
- Owner, reviewer and viewer roles
- Tenant isolation and scoped project access
- Independent review, rejection and revocation
- Encrypted control-plane backup and restore tooling
REVIEW BOUNDARIESIllustration
ProjectAnalytics workspace
ScopedEnvironmentExact review allowlist
ExplicitDecisionDifferent verified account
IndependentChanged scope or access makes prior approval non-current.
FROM SIGNAL TO SHARED UNDERSTANDING
A clearer next step.
At every step.
Start with metadata and observations. Build context before a recovery decision, and keep the review trail with it.
- 01
Bring the evidence
Create a workspace, import a supported dbt manifest and discover permitted PostgreSQL schemas.
OUTPUT A shared catalog - 02
Trace the issue
Inspect run results, freshness and Airflow captures. Identify potential downstream exposure and coverage gaps.
OUTPUT Investigation context - 03
Declare the response
Prepare a bounded plan, map exact tasks and declare the intended write scope and expected outcomes.
OUTPUT An inspectable proposal - 04
Preserve the review
Save immutable contract versions, attach local observations and record a separate account’s decision.
OUTPUT A durable decision trail
This workflow prepares and reviews a recovery response. Live Airflow mutation and automatic recovery are not enabled.
RECOVERY DESERVES MORE THAN A RETRY BUTTON
A decision you
can come back to.
Capture what the team intended, which evidence was attached and who reviewed the exact version. Keep uncertainty visible as the context changes.
View preview statusDeclare
Exact tasks, interval, logical write relations and typed expected outcomes.
Measure
Compare explicitly mapped local artifact bytes with a declared digest.
Version
Preserve the contract and exact attached report behind an immutable binding.
Review
A different verified account records a decision. New versions and stale evidence invalidate current approval.
Review is a human control. Execution is a separate gate.
A local artifact match does not attest deployed-worker code. A recorded approval does not prove safe writes or recovery. Certified execution adapters and production validation remain pending.
CONTROL IS PART OF THE WORKFLOW
Built around boundaries.
Honest about uncertainty.
Controls for teams building toward production operations, with the remaining acceptance gates stated openly.
Tenant & project boundaries
PostgreSQL tenant row-level security, scoped project access and a limited runtime database role.
Explicit review access
Owner, reviewer and viewer roles, with exact environment allowlists for review actions.
Independent decisions
Separate-account reviews, immutable history, cancellation and revocation. Changed context makes approval stale.
Host-held credentials
Optional customer-host Airflow preflight keeps source credentials local. Local artifact reports exclude paths and source bytes.
Evidence with provenance
Distinguish imported results, retained observations, declared dependencies and operator-supplied local measurements.
Control-plane recovery tooling
Encrypted backups, isolated restore drills, PITR and optional off-host tooling for FlowSentra’s own PostgreSQL cluster. Installation diagnostics are operator-restricted. Failed restore drills provide sanitized troubleshooting reasons. Local S3 emulation provides separate development evidence; AWS recovery requires independent validation.
Read our internal security review scope, validation limits and private reporting process →
Production readiness is an acceptance gate.
Real PostgreSQL/runtime-role, TLS/provider, AWS/Docker recovery and authenticated browser validation remain pending. Control-plane backup tooling does not automatically back up connected customer databases. Live SSO sign-in is not enabled.
A FOCUSED FOUNDATION
Built in layers.
Clear about the stage.
Start with PostgreSQL + dbt + Airflow. Expand the platform one verified capability at a time. This is the FlowSentra product website. The hosted application is not available on this site yet.
Development previewIMPLEMENTED IN THE PREVIEW
Understand, investigate, plan and review
Catalog, declared lineage, dbt evidence, read-only discovery and scheduled Airflow collection with a separate operator worker, freshness/contracts, incident workflows and versioned independent reviews. Reported pipeline failures feed a deduplicated inbox with owner triage and linked evidence. Verified owners can opt in to alert emails with bounded retries, relay acceptance history and saved relay-reported delivery, bounce and complaint outcomes. Separate operator delivery/reconciliation workers and a compatible mail relay are required. Verified owners can review record ages and download bounded monitoring metadata exports with checksum receipts; automatic pruning remains future work. Accepted relay bounce/complaint feedback stops further alert emails to that recipient across the workspace, with owner-only bounce review. New failed runs join grouped investigations with assignment, acknowledgement and retained activity history. Grouping is operational context, not a root-cause or recovery claim. Verified owners and assigned reviewers can link retained dbt runs, source-freshness runs and freshness-contract evaluations to the same-environment investigation, with original snapshot references and immutable association notes. Original reported node results, freshness measurements and the pinned contract assessment can be inspected within the investigation using paginated results. These links are human-declared context, not proof of causation or recovery. Project acknowledgement deadlines flag unattended cases; a separate escalation worker can record one overdue escalation and, with additional owner opt-in, queue an email.
ACCEPTANCE STILL REQUIRED
Real infrastructure & production validation
A disposable local PostgreSQL integration workflow is available for operators. Current-release runtime-role integration, concurrent behavior, TLS/provider compatibility, recovery drills and authenticated browser/accessibility acceptance still require recorded validation.
PLANNED OR DISABLED
Execution, more platforms and paid activation
Email-based account recovery needs configured delivery; local development also supports an explicit Docker-operator recovery command. Live recovery dispatch, authenticated deployment evidence, warehouse expansion, live SSO and commercial billing remain future work.
GET CONTEXT BEFORE COMMITMENT
Start with the preview.
Understand your usage.
Self-service onboarding today. Usage-based pricing is planned, with rates and paid activation presented before billing begins.
Get your first shared view.
Free during preview
Start with guided account and workspace setup. Project-specific next steps lead you to catalog imports and reported pipeline results.
- Create your workspace and first project
- Import supported dbt artifacts
- Explore catalog, evidence and planning
- Invite teammates and scope review access
- No card collection or preview charges
Know what you’re using.
A product that grows
with your data operations.
Metadata imports are counted in the workspace usage view. Duplicate imports do not add usage. Commercial rates, paid plans and invoicing are not activated.
No surprise activation.
A few useful answers Rates and paid terms will be presented before billing starts. There is no production SLA or enterprise service commitment in this development preview.
A LITTLE MORE CONTEXT
Good questions.
Clear answers.
The current scope, the operating boundaries and what to expect from the preview.
Which tools can I start with?
Start with PostgreSQL schema metadata, supported PostgreSQL dbt manifest v12 and paired run-results v6 artifacts, plus read-only Airflow API v2 observations targeting 3.1.x. Customer-host selected-metadata eligibility diagnostics use 3.1.6 fixtures. Live version/auth/TLS certification remains pending; warehouses are planned later.
Does FlowSentra query my business data?
Current discovery reads permitted PostgreSQL catalog metadata such as schemas, relations and columns. The dbt import path excludes raw/compiled SQL and row data. Local artifact measurement hashes explicitly mapped local files and produces a path-free report; it does not execute source code. These boundaries apply to the implemented capabilities, not a promise about every future connector.
Will it automatically recover failed pipelines?
No. Live Airflow mutation and workflow dispatch remain disabled. Current recovery capabilities support static planning, evidence checks, immutable reviews and fixed-adapter rehearsals. Human approval and local hash matches do not certify recovery or unlock execution.
Does the backup tooling protect my connected databases?
The implemented recovery tooling protects FlowSentra’s own local PostgreSQL control-plane cluster. It does not automatically back up customer source databases. Real AWS/Docker restore validation remains a production acceptance gate. Point-in-time recovery must also pass a real before/after transaction test.
How does independent review work?
An owner saves an exact contract version and optional local artifact report. A different verified account with project/environment review access inspects it and records a decision. Newer versions, expired evidence, revoked membership or changed access make earlier approval non-current. Review remains non-operational.
Can I sign up myself, and will I be charged?
Yes. Production onboarding checks your emailed one-time code before asking for account and workspace details, then rechecks and consumes it when creating the workspace. Local development without mail permits clearly labeled unverified signup. Direct Resend integration can send signup, verification and reset codes to customer inboxes after the operator verifies a sending domain, configures credentials and starts the separate mail worker. A development-only inbox also supports local testing without external email delivery. Operators receive sanitized guidance for configuration and provider failures while private account codes stay out of routine delivery logs. Branded account emails explain the Spekra relationship and include readable codes with a plain-text fallback. The preview is free and collects no card. A persistent workspace header keeps your project selection and account details available while you switch sections. On desktop, collapse the sidebar to an icon rail for more room to inspect evidence. Projects and retained dbt artifacts have development limits, visible to owners in Usage. Other storage and retention controls remain in development. Usage-based pricing is planned, with paid rates and activation presented first.
YOUR NEXT INCIDENT CAN START WITH MORE CONTEXT
Connect the evidence.
Find your way forward.
Start with a workspace. Build toward a reviewable response.