Get Started
Build your own database frontend app
Database Frontend that lets you give non-engineers a safe surface over production data. Runs on the data you already have. Role-based access included.
Build secure app fast
Build secure app fast
.jpeg)
One GUI, every engine
Connect PostgreSQL, MySQL, SQL Server, Snowflake, BigQuery and more, and manage every one of them through the same SQL GUI.
.jpeg)
SQL or visual queries
Drop into raw SQL for the complex work or build views point-and-click. Both run live against your databases.
.jpeg)
Granular user permissions
Give each role precise read and write access down to the column, across every SQL database you connect.
.jpeg)
Relationships and joins
Navigate across related tables using the foreign keys your SQL schema already defines, with no manual wiring.
.jpeg)
Write-back, no data copy
Every edit writes back to your SQL database in real time. Jet builds on the data where it already lives.
Similar Use Cases
No items found.
.svg-min.png){kind=icon}
.png)
.png)
.png)
Frequently asked questions
What is a database frontend?
An interface that lets people work with data in a database without a database client — forms, tables and views shaped for the person using them rather than for the schema.
Who is it for?
The people who need the data but should not have a SQL console: operations, support, finance. Giving them read-write access to production through a client is the risk this removes.
Does it work with our schema as it is?
Yes. The interface is generated from your live schema and then shaped — relabel fields, resolve foreign keys to names, hide the columns nobody outside engineering needs.
Can we restrict what people can change?
Yes, by table, row and field. Someone can be able to update a status without being able to touch a price.
Which databases are supported?
PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, MongoDB and others, plus warehouses and REST APIs, so one interface can span more than one source.
