Bright lights, big data!
Hyper for Neon
Look at your Neon Postgres projects and run SQL on their databases, as you.
How Hyper works with Neon
What Hyper reads
Hyper does not keep a copy of your Neon data. It reads Neon each time you ask. It can see your own projects, your organizations' projects, and projects that other people share with you. It can list projects, branches, databases, and tables, read a table's schema, compare the schema of two branches, find slow queries, check a database for problems, and read Neon's docs.
What Hyper can do
Run SQL on a database, one statement or many in one transaction. Explain how a query runs. To explain a query, Neon runs it, so explaining a change also makes the change. Hyper cannot create, delete, or reset projects or branches, and it cannot get connection strings. Hyper asks you before each action. You cannot choose to always allow these actions.
Before you connect
SQL from Hyper can change or delete any data that your Neon role can change, and Hyper does not limit it to reading. When you connect, Neon lets you choose read-only access. Choose it if you do not need Hyper to change data. Neon recommends that you use this connection only for development databases, not production. A change that SQL makes is permanent, unless you restore the branch from Neon's history. Anyone who can write data into your database can add text that hides instructions that try to trick an assistant, so check each change before you approve it.