Free · Read-only · No SQL needed

Your database, explained. Free.

For managers and owners — no SQL needed. Connect PostgreSQL or MySQL with read-only access and get your database explained in plain words, with exact numbers.

Public sample databases. The rental shop’s data is from 2022.

DVD rental shop (sample)

PostgreSQL · Measured Oct 12, 2026

Read-only: STYD never changes your database.

This database keeps track of a rental service that lends out films to customers. It records details about customers, the films available, rental transactions, payments, and staff involved in the process.

How it works

  1. rents
  2. is paid for
  3. is managed in

Also here:

What it’s probably used for

This seems to be the backend of a film rental service, probably used to manage inventory, customer rentals, and payments. It likely supports a video rental store or an online rental platform.

Tables

15

Records in total

49,636

Oldest record

Mar 2026

Latest activity

Oct 2026

What stands out

  • Most of your data stopped updating in March 2026, while film kept going until October 2026.

What it can tell you

  • Which customers have rented films and their rental history.
  • The availability and classification of films by category and language.
  • How much revenue has been generated from rentals through payments.
  • Which staff members handled rentals and payments.
  • Where stores are located and their management details.

Questions you can ask

Ask this about your own database — sign up free

Ideas you could build

  • Rental Activity Dashboardreport

    A dashboard showing rental trends, popular films, and customer activity over time.

  • Revenue Summary Reportreport

    A regular summary of payments received, highlighting peak revenue periods and payment methods.

  • Late Rental Return Alertautomation

    Automatically notify staff when a rental is overdue to improve customer service and inventory management.

  • Staff Performance Reportreport

    A report showing which staff members handle the most rentals and payments, helping with management decisions.

Want something built on this data?

Is it safe?

  • Read-only: connect with a read-only database user. STYD never changes anything in your database.
  • What is stored: table and column names, how many records each table has, its first and last dates, and how the tables link. Never the contents of your rows.
  • The AI never sees your values: the written explanation is made from table and column names and a rough size of each table — never a row, never a number from your data.
  • Every number on the report is counted by the database itself, not written by the AI.
  • PostgreSQL and MySQL.
Privacy policy →
Run it on your own database — free