SuperDB

{
  "alternatives": [],
  "artifacts": [
    {
      "binary": [
        "super"
      ],
      "target": "$HOMEBREW_PREFIX/bin/super"
    }
  ],
  "auto_updates": null,
  "categories": [],
  "deprecated": 0,
  "deprecation_reason": null,
  "desc": "Analytics database that fuses structured and semi-structured data",
  "disable_reason": null,
  "disabled": 0,
  "display_name": "SuperDB",
  "enrichment_fetched_at": "2026-06-20T22:49:57+00:00",
  "first_seen": "2026-06-20T00:47:34+00:00",
  "full_token": "super",
  "github_default_branch": "main",
  "github_last_commit_at": "2026-06-19T23:46:52Z",
  "github_readme_excerpt": "# SuperDB [![Tests][tests-img]][tests] [![GoPkg][gopkg-img]][gopkg]\n\n[SuperDB](https://superdb.org/)\nis a new analytics database that supports relational tables and JSON\non an equal footing.  It shines when it comes to data wrangling where\nyou need to explore or process large eclectic data sets.  It\u0027s also pretty\ndecent at analytics and\n[search use cases](https://superdb.org/super-sql/operators/search.html).\n\nUnlike other relational systems that do performance-fragile \"schema inference\" of JSON,\nSuperDB won\u0027t fall over if you throw a bunch of eclectic JSON at it.\nYou can easily do\n[schema inference if you want](https://superdb.org/super-sql/operators/fuse.html),\nbut data is ingested by default in its natural form no matter how much heterogeneity\nit might have.  And unlike systems based on the document data model,\nevery value in SuperDB is strongly and dynamically typed thus providing the\nbest of both worlds: the flexibility of the document model and\nthe efficiency and performance of the relational model.\n\nIn SuperDB\u0027s SQL dialect, there are no \"JSON columns\" so there isn\u0027t a \"relational\nway to do things\" and a different \"JSON way to do things\".  Instead of having\na relational type system for structured data and completely separate JSON type\nsystem for semi-structured data,\nall data handled by SuperDB (e.g., JSON, CSV, Parquet files, Arrow streams, relational tables, etc) is automatically massaged into\n[super-structured data](https://superdb.org/intro.html#super-structured-data)\nform.  This super-structured data is then processed by a runtime that simultaneously\nsupports the statically-typed relational model and the dynamically-typed\nJSON data model in a unified compute engine.\n\n## SuperSQL\n\nSuperDB uses SQL as its query language, but it\u0027s a SQL that has been extended\nwith [pipe syntax](https://research.google/pubs/sql-has-problems-we-can-fix-them-pipe-syntax-in-sql/)\nand [lots of fun shortcuts](https://superdb.org/super-sql/operators/intro.html#shortcuts).\nThis exte",
  "github_repo": "brimdata/super",
  "github_stars": 1557,
  "github_topics": [],
  "homepage": "https://github.com/brimdata/super",
  "homepage_og_description": null,
  "homepage_og_image": null,
  "homepage_title": null,
  "installs_30d": 4,
  "installs_365d": 38,
  "installs_90d": 38,
  "last_seen": "2026-06-20T00:47:34+00:00",
  "llm_generated_at": null,
  "llm_model": null,
  "names": [
    "SuperDB"
  ],
  "one_liner": null,
  "rank_30d": 5954,
  "rank_365d": 6559,
  "rank_90d": 3743,
  "raw_hash": "f551c6f173270bf2",
  "ruby_source_path": "Casks/s/super.rb",
  "tap": "homebrew/cask",
  "token": "super",
  "version": "0.3.0",
  "why_use_this": null
}