LandingLens on Snowflake
LandingLens vs. LandingLens on Snowflake
This article applies to these versions of LandingLens:
LandingLens | LandingLens on Snowflake |
---|---|
For the most part, the experience using is the same as using LandingLens directly from LandingAI. In both, you will upload and label images, and then train and deploy computer vision models.
If you’re using , you get the exclusive benefits of data governance, Snowflake Copilot, and more.
If you’ve used LandingLens from LandingAI before, you might notice that some features are different or absent. Some features and concepts are not relevant when using LandingLens in Snowflake, because Snowflake inherently provides those concepts or handles them differently.
The following table lists concepts that aren’t found in because they are handled differently by Snowflake
Concept or Feature | Description |
---|---|
LandingLens credits, pricing plans, and billing | Credits, pricing, and billing are managed in Snowflake. |
LandingLens API keys | Authentication is managed in Snowflake. |
LandingLens members and roles | Access to LandingLens is managed using the secure and granular access controls in Snowflake. |
Examples page and Load Sample Data | users can access sample datasets by getting these apps in the Snowflake Marketplace: |
Other differences between LandingLens and are marked throughout the documentation.