Why WhereScape?

WhereScape addresses end-to-end data warehouse automation, modeling (including Data Vault 2.0), orchestration, environment promotion, documentation + lineage and governed changes – it goes far beyond just ELT transforms or ingestion.

Use WhereScape to standardise patterns, speed refractors and keep design, code and documentation in lockstep; whether you choose to keep dbt + Fivetran in the mix, or not.

You get a model-first, metadata-driven approach that generates consistent SSIS-free ELT or SQL scripts and manages change across Dev/Test/Production environments with versioning and rollback. 

You’ll be able to greatly reduce the need for time-consuming manual coding, standardize your own workflows and create portable designs, ready for if you later migrate from SQL Server to Snowflake, Databricks or Microsoft Fabric. Replace your spaghetti code with more maintainable and flexible solutions.

WhereScape provides very broad coverage across databases, files, cloud warehouses and data lakes. It’s so broad that an easier way to think about it is, if the platform you have in-mind can connect via native drivers, ODBC/JDBC or cloud connectors, then WhereScape can typically ingest and generate for it.

If you want to speak about your specific stack, get in touch and we can confirm the support of specific versions.

It’s simple, you define the rules that WhereScape needs to enforce and we will do it with consistency. This way, you can choose whether to flag sensitive attributes or choose whether to apply masking, encryption, tokenization, deletion or segregation into specified restricted schemas.

And because the logic is metadata-driven, policy changes propagate consistently through generated code and documentation ready to be audited.

Yes, we do via metadata import/export and APIs. Common workflows we see from customers include pushing lineage or technical metadata to catalogs or importing catalogued sources to seed models.

Coverage varies by catalog: we can align to the integration approach that your team prefers, whether that happens to be via export, API or partner add-ons.

Yes, we do: you can store metadata in Git, using branching/PRs for change control and automate CI/CD to promote artifacts across different environments.

Our customers integrate with Azure DevOps, GitHub and Jenkins to standardize their releases.

We don’t provide rigid, one-size-fits-all industry models because we know that every environment is unique.

However, we do bring decades of experience in sectors including finance, education, healthcare and manufacturing – and that experience comes with a network of partners who specialise in these sectors and others, so if it is desired; we can introduce you to the perfect partner to suit your needs.

WhereScape supports Data Mesh by enabling domain teams to design and publish reusable and well-documented data products, all with consistent standards.

Automation makes it easier to apply common patterns e.g. naming SCD/CDC, enforcing data governance by-design and sharing lineage/SLAs across domains.

Yes, WhereScape has supported Data Vault automation for almost two decades: both the Raw Vault and the Business Vault.

It works like this: you define the business rules at the logical layer, then WhereScape generates the Raw Vault and Business Vault artifacts and documents the transformations for audit and reuse.

No, we have so many customers that come to us that know they want to move but haven’t decided on ‘where’. It’s simple, you start wherever you are today and we will help keep your designs portable.

Then, given time, once you’ve selected a target platform; then you can migrate with far less rework because patterns and lineage have already been standardized. We see a lot of customers starting on SQL Server and moving to Snowflake, Databricks, Synapse or Fabric – but we support many other supported platforms beyond those.