Skip to main content

This guide is for the Snowflake administrator (ACCOUNTADMIN) of an account where Genesis runs as a Snowflake Native App. The default app name is GENESIS_DATA_AGENTS. If you installed it under another name, use that name in every command below.

Before you start

  • Back up the encryption master key before uninstalling if you enabled encryption. In Genesis, open Config → Secrets and use Back up key to save a copy of GENESIS_SECRETS.PUBLIC.GENESIS_ENCRYPTION_KEY in your own secret store. See Secrets — encryption setup and status.
  • Export anything you want to keep. Everything inside Genesis is deleted permanently. Export threads, agents or missions from Genesis, or take a full snapshot to S3/GCS (Genesis 1.19.95+).
  • Check your event table. Run SHOW PARAMETERS LIKE 'EVENT_TABLE' IN ACCOUNT;. If it points into a database you will drop below, run ALTER ACCOUNT UNSET EVENT_TABLE; first.
1

Uninstall the app

First list what the app owns outside itself, so nothing you want to keep is dropped unseen:
Then drop the app:
Or in Snowsight: Catalog › Apps › … › Uninstall, then choose “No, delete all objects created outside the app”.This removes:
  • the app and all its data: threads, agents, missions, knowledge, files, connections, stored credentials, users and settings
  • the compute pool GENESIS_DATA_AGENTS_POOL and its running service
  • the warehouse GENESIS_XSMALL
  • the service endpoint integration (SNOWSERVICE-…)
  • any database the app created, including ones agents built
  • every grant you gave the app, and its event-sharing settings
This also deletes databases the app created. If you want to keep one, transfer its ownership to one of your roles first. The uninstall cannot be undone.
2

Optional cleanup

These objects were created by your team, not by the app, so they stay behind. Open each question that applies to you. Each block is already in the right order.
A secrets database with the key, its network rule and an external access integration remain.
Snowsight created one external access integration per connection you approved. It also created a database that holds their network rules.
The helper database GENESIS_LOCAL_DB remains, along with any key-pair secret you bound to Genesis. Your team may also have put other things in it, such as the account event table. Look inside before you drop it.
A network rule for the Genesis compute pool remains, and it is still listed in your account network policy.
If the Genesis rule is the only rule in the policy’s allowed list, the list cannot simply be emptied. Decide with the policy’s owner how to replace or retire the policy before you drop the rule.
The service user and its access token remain, along with its network policy and two network rules.
A database holding your Tailscale auth key remains.
One OAuth security integration per connection remains.
The relay’s service user and its role remain.
The workload-identity secret remains. The SECURITY_DB database may be shared with other tools, so keep it unless only Genesis used it.
A service user and role created for remote app access remain.
Sharing stops when the app is dropped. Your account event table stays, and so do events already shared with Genesis. Ask Genesis support if you want those deleted.
These stay as they are. They include:
  • a warehouse you gave Genesis;
  • Cortex model roles you granted to your own roles;
  • an RSA key you added to a user for a Genesis connection;
  • optimization-demo databases (CLI805_OPT_…).
Remove only what nothing else uses.
3

Confirm it's clean (optional)

Anything still listed is either something you chose to keep or something to review. Objects you named yourself (a warehouse, secret, role or user without GENESIS in its name) will not show up here, so check those by name.
Snowflake references: DROP APPLICATION · Uninstall a Native App · Manage apps · Set up event tracing for an app