Developer Lab
Live runtime · real database

Spring Boot with a Real PostgreSQL Database Behind It

A database of your own that is still there tomorrow — not an in-memory one that vanishes when the app stops. Browse and edit its tables, run SQL against it, and point a running Spring Boot project straight at it.

  • Real PostgreSQL
  • Persists between runs
  • Browse & edit tables
  • SQL console
  • CRUD in one click
🪙 Buy tokens
Your last workspace
Open workspace

Pre-built with a database

Fastest

A working CRUD service on PostgreSQL — users, roles and an audit trail, seeded on first run. Read it, run it, change it.

  • Three tables created and seeded for you
  • GET / POST / PUT / DELETE over the users table
  • The connection written into application.yml, not hidden
  • Swap the database later and run again
Pick one of yours, or create a new one.

Prepare a database

Your schema

Name a database, give it your own tables, and get a Spring Boot project already pointed at it.

  • Your CREATE TABLE statements, run as you
  • A Spring Boot + PostgreSQL starter on top
  • The connection written into application.yml
Runs as your own database role. Leave it empty to start with no tables.

How it works

  1. 1Pick a way in A ready-made CRUD app, or your own tables
  2. 2A database is created Yours alone, on a shared PostgreSQL server
  3. 3The project is wired to it Written into application.yml, not hidden
  4. 4Run it Builds and boots with its own live URL
  5. 5Hibernate creates the tables And the seeder fills them on first run
  6. 6Browse and edit the data Tables panel: add, update, delete rows
  7. 7It is still there tomorrow Stop the app; the data stays

Both routes open the workspace, where you can edit the code, browse and edit your tables, run SQL, and start or stop the service. The plain Spring Boot Sandbox is unchanged and has no database.