Snowflake

Both products carry the identical object contract, so a query written against the free sample runs unchanged against the complete register. Only the row counts and the database name differ.

Products ship on Snowflake Marketplace as Secure shares. The Philippines AML/CFT free sample is a Free Listing. Get it from the Marketplace with no purchase step. The complete register and other paid products are Marketplace purchases of the same Secure share product type.

1. Open the listing on Snowflake Marketplace and get the Free Listing or complete the paid purchase.
2. Mount the Secure share from the listing. A role with IMPORT SHARE (or the Marketplace get flow) creates the database under a name you choose.
3. Choose the database name. The name is yours to pick at mount time, which is why every example on these pages uses the portable REGULATORY.OBJECT form rather than a fully qualified path.
4. Select the database and a warehouse in a worksheet, then query the REGULATORY schema.

Confirm the mount, then let the notebooks do the demonstrating.

1. Run SHOW VIEWS IN SCHEMA REGULATORY; in a worksheet. Fourteen secure views means the mount is healthy. An empty result means the querying role is missing usage on the schema, not that the share is empty.
2. Read the RELEASES view into your own metadata table, so a downstream consumer can prove which snapshot an analysis ran against.
3. Run the listing's SQL examples against your mount. They are the working tour of the register and the graph; see SQL Examples.

The object catalog, the column reference, and the knowledge graph are documented per product, because they are properties of what you license rather than of the channel. Start with the free sample's documentation, whose contents anyone can already download and evaluate.

Snowflake listings no longer support attached notebooks, so every product ships its working examples as validated SQL on the listing itself. Each product page reproduces its listing's examples in full, and every query addresses objects as SCHEMA.OBJECT so it runs unchanged against your mount.

The examples are compliance workflows rather than demonstrations. An obligation brief, a full register review, an auditor evidence matrix, a coverage workpaper, and the conditions and exceptions that change what applies.

Releases are versioned point-in-time snapshots, reissued quarterly and whenever the regulator amends a covered instrument and the amendment has been ingested and recertified. A refresh replaces the secure views in place and preserves existing grants, so a consumer does not remount anything.

Existing columns are not repurposed. Additive objects and columns may appear in a later release. A breaking change is delivered as a separately named product line with advance notice, never as a surprise in an existing share.