Data Catalog Software That Doesn't Need Babysitting to Stay Useful

Engineering-friendly authoring (Git-native, API-first, programmatic), faster deployment (24 hours to auto-discovered catalog vs 12-18 months for Collibra), lower TCO at scale, and a strong active-metadata story. Atlan is the closest competitor in modern positioning; Logiciel differentiates on broader scope (catalog plus quality plus pipeline observability plus cost), engineering ergonomics (Terraform, CI/CD, code-reviewed metadata), and integrated governance enforcement. Collibra and Alation are mature stewardship platforms - capable but bureaucratic. Most customers replacing those tools consolidate 2-3 EDM line items into Logiciel with 40-60% TCO reduction. We don't compete on enterprise stewardship workflow depth; for the 95% of US enterprise needs, our trade-offs win.

We parse query logs (Snowflake, Databricks, BigQuery, Redshift query history), dbt manifests, Airflow DAGs, Python instrumentation, and BI tool metadata (Looker LookML, Tableau workbooks, Mode notebooks) to derive column-level lineage automatically. No manual declaration required; lineage updates continuously as new query logs arrive (typically within 5-15 minutes). For non-SQL transformations (Python, Spark), SDK instrumentation captures lineage at runtime with 1-3 lines of code per script. Accuracy is typically 95%+ for SQL-heavy stacks. Lineage is queryable via API for downstream tools - impact analysis, audit reports, change management, AI agents needing governed access.

Semantic search with recommendations, certified-asset workflows, and a clean UX designed for analysts and stewards rather than engineers. Business users search by business term ('revenue', 'churn rate', 'active customer'), see certified assets ranked first, view lineage as a visual graph, and propose changes through governed workflows. Glossary curation is structured (definition, owner, classification, examples) without being bureaucratic. For self-service analytics teams, Logiciel typically reduces time-to-find-the-right-table from days to minutes - measurable in stakeholder satisfaction surveys and reduced 'where do I find X' Slack messages. AI-powered search recommendations improve over time as usage patterns establish.

Connect your warehouse and BI tool - 24 hours later, you have an auto-discovered catalog of your top 500 assets with column-level lineage. The first week is baseline establishment and tuning; weeks 2-4 are governance configuration (classifications, glossary, ownership) and stakeholder onboarding; by day 30, most teams have a fully populated catalog covering their most-used 1,000-5,000 assets with active stewardship workflows. ROI in the first quarter is typically expressed as analyst time saved (faster discovery), reduced 'where do I find X' overhead, and improved data trust (certified assets ranked first reduces use of stale data). Most customers consolidate 2-3 ad-hoc tools into Logiciel within 6 months.

Yes - migration tooling for Atlan, Collibra, Alation, IBM Cloud Pak for Data, Informatica, and other major catalogs. Migration extracts metadata, lineage, glossary, and governance policies from your existing catalog, ingesting into Logiciel while preserving user-facing context. Migration runs in parallel: Logiciel ingests metadata while continuing to honor existing user workflows; over 6-12 months, business users transition to Logiciel's UI and the legacy catalog is retired. Migration is fixed-fee scoped to your catalog footprint. About 60% of customers retire the legacy after 12 months; 40% keep the legacy as a search front-end while Logiciel becomes the metadata of record. Either pattern works.

Python and Spark instrumentation cover those - typically 1-3 lines of code per script to capture lineage at runtime. The SDK wraps DataFrame and Spark operations to track inputs and outputs at the column level. For dbt-Python models, lineage is derived automatically from model definitions. For ad-hoc Python scripts (Pandas transforms, ML feature engineering, custom ETL), the SDK provides drop-in instrumentation. Declarative APIs cover edge cases where instrumentation is impractical (closed-source systems, third-party scripts) - you can declare lineage manually with versioned manifests. We don't require declarative lineage for everything; instrumentation coverage is typically 95%+ for Python-heavy stacks.

Yes - first 500 assets free, forever. The free tier includes auto-discovery, column-level lineage, basic search, business glossary, and read-only API access on those 500 assets. No credit card, no time limit. About 30% of free-tier users convert to paid within 6 months when their asset count outgrows 500 or when they want enterprise features (advanced governance, custom workflows, SSO, audit logging). The other 70% stay free, which is the design intent - making catalog accessible to teams that can't budget enterprise tooling but still need their data discoverable. Free tier is functionally complete for small teams; enterprise tier adds the governance and operations layers.