DocsDeploy & operate

Admin UI

A dashboard for every collection, and for running the server, at /_/.

Every Sluurp server has a dashboard at /_/, like Django admin: made from your schema, with no code. Each collection gets a table to browse, filter and edit, and there are screens to run the server. To open it, start the server and go to /_/:

sluurp serve --public ./app
# Admin:   http://localhost:8090/_/

Features include:

  • A table and a form for every collection, updated live as others change records
  • History, undo and a recycle bin for every record
  • Logs searched with KQL, an SQL console, backups, jobs and rate limits
  • Live charts of traffic, and watches that raise alerts
  • An API screen to try any endpoint as yourself

For your data

  • A table per collection with a filter box (paid = true && total > 100), sorting, a column picker and paging.
  • A form per record with the right input for each field: date pickers, relation pickers you can search, and image preview and upload.
  • History and undo: every change with who and why, any version restored, and deleted records in a recycle bin.
  • Explore and pivot tables, charts and formulas over a collection, with no export needed (install the explore plugin).
  • Rules for read and write access, edited next to the collection.

For the server

Logs, SQL console, backups, scheduled jobs, rate limits, mail, sign-in providers, payments, forms, feeds, translations and storage, each on its own screen. System shows traffic, response times, storage, releases and the lists browsers keep synced. Administrators, under Platform, lists who can sign in to the admin; add one there, or remove one, except the last. Reorder the Platform items by dragging or with Alt+arrow keys. A group with more than one entry folds and unfolds by its name. Ctrl+K (⌘K) jumps to any screen, collection or record.

System’s charts are live: requests and response times a minute at a time over the last six hours, sliding as time passes, the minute under way filling in as it goes. Point at one for that minute’s values.

Watches

Also on System, watches look at the server’s measures once a minute: the mean or slowest response time, requests or server errors a minute, and the share of requests that fail. A watch fires when its measure, over the last few minutes, is above a number you set, or unusual: well above what the hour before it was. It raises an alert, which is logged and heard by any agent that watches alert, and mails the address you give. It fires once, and again only after the measure has been back to ordinary.

Preferences

Your own settings for the admin, kept with your account, from the menu under your name:

  • Sidebar: which groups (Platform, Extensions, Collections, Managed) and which screens it lists. A screen left out still opens from Ctrl+K.
  • UI testing: the devices the Storyboard’s Playground and Hawkeye offer their frames as, by name and size in CSS pixels. Add, change or remove them, or go back to the defaults. A frame or a pinned preview dragged near one of their sizes snaps to it.

Logs

Every request is logged: time, method, path, status, duration, user and IP. Search them with Kibana’s query language (KQL):

status:5xx and path:/api/*
method:POST or took>500
not who:_superusers* and (status:4xx or status:5xx)
time>=2026-09-20 and time<now-2h
timeout 10.0.0.7
  • field:value matches: status by class (2xx) or code, method exactly, path, who and ip by substring, or by wildcard with *.
  • =, !=, >, >=, <, <= compare. time accepts a date, a datetime, or now-15m, now-2h, now-7d.
  • Combine with and, or, not and parentheses. Terms side by side must all match. A bare word matches anywhere.

The database keeps one week of logs. Older entries are archived to a gzipped file per day (logs/2026-09-18.jsonl.gz in the data directory), kept for 90 days. A search over a longer window includes the archives by itself.

API

The API screen lists every endpoint from the project’s OpenAPI document, grouped by collection. Choose one, fill in its parameters and body (filled in from the collection’s fields), and send it as yourself. You see the status, the time and the response, and can copy the request as curl or download openapi.json for a client generator.

Storyboard

With the Storyboard plugin installed, the Storyboard screen is a component workshop, like Storybook: docs, a playground and tests for the kit’s components and your own. See Storyboard.

Hawkeye

With the Hawkeye plugin installed, the Hawkeye screen shows your site in a frame per device, with the code and data of any component you target. See Hawkeye.

Compared with Django admin

Sluurp has, Django admin doesn’t:

  • Live updates: records changed by others update on your screen.
  • Built-in history, restore and recycle bin for every collection.
  • SQL console, backups, logs, jobs and rate limits in one place.
  • Nothing to register: a collection appears as soon as it exists.
  • Collaborative live translation editing.

Django admin has, Sluurp doesn’t (yet):

  • Per-model customisation of the standard form in code: visible columns, form grouping. (You can add your own screens, cards, record actions, bulk actions and editors with admin extensions.)
  • Inline editing of related records in the parent form.
  • Date drill-down (year → month → day) above lists.

The admin is a React app built with the same components your apps use.

View as Markdown