# Shipping a Data Catalog App on Snowflake App Runtime: Notes From a Real Build

DevFeed: [Shipping a Data Catalog App on Snowflake App Runtime: Notes From a Real Build](<https://devfeed.tech/articles/shipping-a-data-catalog-app-on-snowflake-app-runtime-notes-from-a-real-build-121770.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/shipping-a-data-catalog-app-on-snowflake-app-runtime-notes-from-a-real-build-2fcc74d4e5c0?source=rss----34b6daafc07---4>)

Author: Augusto Rosa

Published: 2026-11-06T22:01:02Z

Content type: article

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Streamlit](<https://devfeed.tech/topics/streamlit.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [application-development](<https://devfeed.tech/tags/application-development.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [cortex](<https://devfeed.tech/tags/cortex.md>), [data-catalog](<https://devfeed.tech/tags/data-catalog.md>), [data-governance](<https://devfeed.tech/tags/data-governance.md>), [data-superhero](<https://devfeed.tech/tags/data-superhero.md>), [dbt](<https://devfeed.tech/tags/dbt.md>), [definition](<https://devfeed.tech/tags/definition.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [next](<https://devfeed.tech/tags/next.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [shipping](<https://devfeed.tech/tags/shipping.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>)

## AI overview

A five-day rebuild moved a Streamlit business glossary and approval app to a Next.js app on Snowflake App Runtime, deployed with `snow app deploy`. The account keeps data in Snowflake and uses existing SSO; identity-aware writes live in the app because Sigma connects through a shared service role. The main constraint is access design: caller's-rights queries require both user privileges and matching CALLER grants held by the app owner, while shared SNOWFLAKE objects such as Cortex functions and GET_LINEAGE require owner's rights. The deploying role becomes the app owner and sets the privilege ceiling, so the article recommends a dedicated, narrowly granted role and setting up grants before building pages. It also describes limits and tradeoffs: lineage shows only metadata visible to the owner, dynamic tables need MONITOR rather than REFERENCES, and steward workflows require real users for acceptance testing. The build sequence provisions Snowflake objects and grants, seeds draft terms from dbt without overwriting human edits, then deploys and grants app usage.

## Source excerpt

Caller's rights, CALLER grants, and the shared objects that refuse to cooperatePhoto by Boitumelo on Unsplash Most data platforms hit a governance problem right when they start working. The dbt models ship, the semantic views exist, the dashboards render. Then someone in finance asks what Net Revenue means in this warehouse and who signed off on it, and nobody has a good answer. Plus, wow, Snowflake App Runtime is pretty amazing: an app very close to your data. tl;dr Over five days I rebuilt a business glossary and definition-approval app on Snowflake App Runtime and deployed it into a client account. It is a Next.js app. It went live with snow app deploy, and nobody had to touch Docker, a container registry, or a separate auth layer. The data stays in the account, and users sign in with the SSO they already have. To be fair, the catalog companion was not my idea. A co-worker built the first version in Streamlit, and I extended it and moved it to App Runtime. The UI was the quick part. Three things that took me the most time to figure out: Caller's rights is two permission checks. A query runs as the signed-in user only if the user's own role allows it and the app's owner role holds a matching CALLER grant. Miss the CALLER grant and the page fails with a "does not exist or not authorized" error that looks like a missing object. Shared objects in the SNOWFLAKE database cannot take CALLER grants. Cortex functions and GET_LINEAGE come back as Unknown user-defined function under caller's rights. Those calls run with owner's rights, and you scope what the owner can see. The owner role sets the ceiling for every user. The role that deploys the app becomes its owner. Deploy as a dedicated role with a short list of grants, and never as SYSADMIN or ACCOUNTADMIN. Get the grants in place first, then write the pages. In that order the build is boring, which is what you want. What I built and why it runs on App Runtime The client is a retailer partway through moving off a legacy