Introducing dpkit Terminal and TypeScriptSee the announcement
Datist

Technologies

What we build on, and why.

Grouped by what they let us do rather than by vendor. Every tool listed is one we run in production — open the capability for the reasoning behind it.

core stackdatist · stack
TypeScript
language
Node
runtime
Postgres
database
React
interface
Everything else is chosen per problem

Data & storage

  • Transactional databases

    One Postgres per product, with the schema and the queries deliberately owned by different tools.

    • PostgreSQL
    • Prisma
    • Kysely
    • SQL migrations
    • pgvector
    • PostGIS

  • Data processing

    Columnar dataframes instead of ad-hoc scripts, so a million rows costs what a thousand does.

    • Polars
    • Parquet
    • Arrow
    • Data Package

  • Data standards & validation

    Schemas that travel with the data, and one validation contract from database to browser.

    • Fairspec
    • Data Package
    • JSON Schema
    • Zod
    • Pydantic
    • DataCite

  • Web data acquisition

    Polite, resumable crawls that fail loudly instead of quietly going empty.

    • Crawlee
    • Playwright
    • Cheerio
    • Firecrawl

Services & integration

  • Durable workflows

    Multi-step processes that resume exactly where they stopped after a crash or a deploy.

    • DBOS
    • Postgres state
    • Cron Triggers

  • Typed APIs

    One definition generating the server, the client and the docs, so drift is a build error.

    • oRPC
    • Connect RPC
    • Protobuf
    • Server functions
    • OpenAPI

  • Identity & access

    Sign-in, organisations and permissions bought in rather than rebuilt badly.

    • Clerk
    • Better Auth
    • OAuth
    • Passkeys

  • AI engineering

    Models behind an interface we control, with retrieval and evaluation around them.

    • OpenRouter
    • AI SDK
    • Mastra
    • MCP
    • pgvector

Product interfaces

  • Full-stack web applications

    Server-rendered React with typed routing and data loading in one project, not two.

    • TanStack Start
    • TanStack Router
    • TanStack Query
    • React
    • Vite

  • Design systems

    Tokens, primitives and accessible behaviour, so the tenth screen looks like the first.

    • Tailwind CSS
    • Base UI
    • shadcn
    • Lucide

  • Internationalization

    Locale in the URL, copy in catalogs, and hreflang that only advertises pages that exist.

    • Lingui
    • ICU MessageFormat
    • PO catalogs
    • hreflang

  • Mobile & desktop

    Native apps sharing the web product's types and rules instead of forking them.

    • Expo
    • React Native
    • EAS
    • Electron

Platform & operations

  • Edge platform

    Static and server-rendered sites running close to the user, and cheap to keep up.

    • Cloudflare Workers
    • R2
    • D1
    • Hyperdrive

  • Container orchestration

    Declared infrastructure on rented metal, for when a product outgrows a serverless bill.

    • Kubernetes
    • Terraform
    • Hetzner Cloud
    • Traefik
    • Docker

  • Observability

    Structured logs, real error reports, and analytics that need no cookie banner.

    • Plausible
    • LogLayer
    • Sentry
    • Structured logs

Engineering practice

  • Automated testing

    Fast unit tests, recorded HTTP, and documentation that fails the build when it goes stale.

    • Vitest
    • Playwright
    • testdocs
    • MSW
    • Codecov

  • Developer tooling & release

    One toolchain across every repository, so moving between them costs nothing.

    • pnpm
    • vite-plus
    • tsgo
    • lefthook
    • uptask
    • fireargs
    • livemark
Get a quote