# From Streamlit to Snowflake App Runtime: A Demo Migration

DevFeed: [From Streamlit to Snowflake App Runtime: A Demo Migration](<https://devfeed.tech/articles/from-streamlit-to-snowflake-app-runtime-a-demo-migration-136381.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/from-streamlit-to-snowflake-app-runtime-a-demo-migration-19e6e81d9873?source=rss----34b6daafc07---4>)

Author: Daan Bakboord

Published: 2026-11-17T01:03:18Z

Content type: tutorial

Language: en

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

Topics: [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [Streamlit](<https://devfeed.tech/topics/streamlit.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [apache-ossie](<https://devfeed.tech/tags/apache-ossie.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [builds](<https://devfeed.tech/tags/builds.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [custom](<https://devfeed.tech/tags/custom.md>), [daanalytics](<https://devfeed.tech/tags/daanalytics.md>), [data-superhero](<https://devfeed.tech/tags/data-superhero.md>), [demo](<https://devfeed.tech/tags/demo.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [error](<https://devfeed.tech/tags/error.md>), [interface](<https://devfeed.tech/tags/interface.md>), [js](<https://devfeed.tech/tags/js.md>), [metric](<https://devfeed.tech/tags/metric.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [migration](<https://devfeed.tech/tags/migration.md>), [moving](<https://devfeed.tech/tags/moving.md>), [next](<https://devfeed.tech/tags/next.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [semantic-view](<https://devfeed.tech/tags/semantic-view.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [streamlit](<https://devfeed.tech/tags/streamlit.md>)

## AI overview

The Apache Ossie demo moved from Streamlit in Snowflake to a Next.js app on Snowflake App Runtime while keeping its SQL, data, and semantic view unchanged. The semantic view implements the metrics queried by the app, so replacing the interface did not require rewriting metric definitions; the demo showed different revenue totals with and without that view (115,550 and 103,200). The author valued App Runtime's control over layout, ordinary links, and server-rendered pages. Streamlit remains a Python-first option when its widgets meet the need; a custom web interface entails owning a separate interface. This was a five-question demo migration, not a performance benchmark or a complete production migration. The excerpt begins describing implementation changes but cuts off before giving further migration or deployment steps.

## Source excerpt

Moving a data app should not change what its numbers mean. I moved the Apache Ossie demo from Streamlit in Snowflake to Snowflake App Runtime to try a different interface around the same metric definitions. This walkthrough covers the Next.js rewrite, deployment and the authentication error I encountered. In the same table, different revenue the demo answered one question twice: 115,550 without a semantic view, 103,200 with it. That demo ran as a Streamlit in Snowflake app. I have now moved it to Snowflake App Runtime, as a Next.js app that Snowflake builds and runs next to the data. The numbers did not move. That was the point of the exercise. The Ossie YAML describes the intended definitions; the Snowflake semantic view implements the metrics queried by the app. Keeping those definitions outside the interface meant I could replace the interface without rewriting them. This is a migration of a small demo, with five comparison questions. It is not a performance benchmark or a complete production migration. The code is in the Apache Ossie demo repository. Why try a different runtime? For this demo, the useful change was control over the interface: ordinary links, server-rendered pages and a custom layout. Streamlit had already made it easy to build the original data app. Moving to Next.js let me shape how readers navigate the explanation and share a particular comparison. I would make that choice based on the application you need to build. If Python widgets already meet the requirement, keeping Streamlit avoids owning a separate web interface. Snowflake describes the distinction in its App Runtime overview: Streamlit offers a Python-first approach, while App Runtime supports custom web applications. For me, the architectural question was whether the metric definitions would survive that change intact. What changed The SQL, the data and the semantic view stayed exactly as they were. Everything between the user and the query changed: one Python app file became a small