Show HN: Base, an SQLite database editor for macOS

Original Article ↗ Hacker News Discussion ↗

Overall Reception

  • Many commenters are long-time users (up to ~15 years) praising Base as their go-to SQLite GUI on macOS.
  • New discoverers are surprised it has existed so long and often say they would have used/bought it earlier if they’d known.
  • Several people immediately buy or plan to buy, especially those wanting a minimal, native Mac SQLite tool.

Why Use Base vs Alternatives

  • Compared to generic multi-DB tools (DBeaver, DataGrip, TablePlus, etc.), Base is praised for:
    • Being purpose-built for SQLite (no irrelevant features like user management, stored procedures, remote connection UX).
    • Good table creation/alter support and SQLite-specific conveniences.
    • Native AppKit/SwiftUI behavior and polish (keyboard/mouse affordances, Finder-like interactions).
  • Versus DB Browser for SQLite:
    • Some prefer DB Browser’s being free, OSS, and cross-platform.
    • Others report instability, locking behavior, or “ugly”/less refined UI there and see Base’s UX polish as a key differentiator.

Platform & Native vs Web

  • Base is macOS-only because it uses AppKit/SwiftUI; cross-compiling to Linux/Windows is seen as non-trivial.
  • Some are disappointed by the lack of cross-platform support and reliance on macOS 15+ for v3, though old versions exist.
  • Thread detours into a heated native-vs-web debate:
    • One side: native desktop tools are faster, more efficient, integrate better, and the web is a poor app platform.
    • Other side: web apps can be good enough or better in practice; on some platforms native ecosystems have atrophied.

Target Audience & Use Cases

  • Use cases mentioned:
    • Exploring and tweaking SQLite DBs used by apps (including Apple system apps).
    • Prototyping schemas and exporting SQL for codebases.
    • Scientific research data storage and analysis; ad‑hoc querying of CSV/exports.
    • Non‑programmers using SQLite as a step up from Excel/Access-like workflows.
  • Some question who needs visual table editors; multiple replies argue GUIs are great for prototyping, learning SQL, and quick schema evolution.

Features, Requests, and Limitations

  • Requests: UUID blob display/editing, auto-enabling foreign keys, extension auto-loading, JSON view, triggers visibility, tabs for multiple queries, better font control, more “diagram”/ERD-like features.
  • Missing features: no SQLCipher support currently; no multi-user collaboration (seen as more of an SQLite limitation).
  • Some see it as “Postico for SQLite”; others wish it matched Postico’s UX in areas like copy/duplicate rows.

Pricing, Licensing, and Business Model

  • Price (~$40 one-time) sparks debate:
    • Some call it expensive for a small utility and lament lack of source code.
    • Others argue the price is trivial relative to developer productivity and indie sustainability.
  • Discussion of closed vs OSS:
    • A few would pay more if it were OSS or source-available.
    • The author cites piracy and legal hassle as reasons not to open the code.
  • Revenue mix: historically App Store-dominant, with recent shift toward more direct sales; product alone does not fully support the developer.