Hype StackHypeStack
Any language, one file each

Speak your users'
language.

Every string in the app and the admin is a typed Paraglide message. A new language is one JSON file, and anything you have not translated yet falls back to English.

Start with the starterSee how a language lands
one codebase, any localetry it
messages/en.jsonfallback: en
How a language lands

One file per language. The whole product follows.

No i18n framework to wire, no provider to mount, no extraction pass. The catalog is already there; you add a locale to it.

  • Register the locale

    step 1

  • Translate the values

    step 2

  • Ship it

    step 3
Typed end to end

Strings that fail the build, not the user.

Paraglide compiles the catalog into typed functions, so the compiler reads your copy the same way it reads your code.

  • Every string is a message function

    m.billing_upgrade_cta()

  • A renamed key stops the build, not the user

    TS2339

  • Untranslated keys fall back to English

    fallback: en

  • Packs merge their copy into your catalog

    messages/en.json

  • Even pack nav labels stay translatable

    sidebar + settings tabs

  • any

    Español
    日本語
    Deutsch
    polski
    Українська
    Português

    Language you want, not a picker list

    locales is your array in project.inlang/settings.json. There is no supported-languages table.

  • 1 file

    messages/pl.json

    app

    admin

    packs

    To add a whole language

    messages/<locale>.json beside the English one. Your locale files are never touched by installs.

  • 0

    teams packmerged
    billing packmerged
    notifications packmerged

    Hardcoded strings in any pack

    Install merges each pack's messages into en.json, and re-running compose produces no diff.

Feature packs to grow with

Every pack ships real source code: frontend, backend, and admin surfaces where the feature needs them. Add them when you need them, one command each.

FeatureWhiteboardA collaborative whiteboard: sticky notes, freehand ink, shapes, images, and layers on one infinite canvas, synced live.Infinite canvasLive multiplayerFeatureTeamsTeam workspaces with members, roles, icons, and email invitations on top of your starter.Team workspacesMember rolesFeatureBilling (Stripe)Stripe integration, subscriptions, billing flows, and an admin revenue widget.Stripe checkout & portalSubscription plansFeatureProjectsOrg-scoped projects with members, favorites, icons, and a navbar switcher.Project CRUDMembers & roles
See all 12 packs

Questions, answered

Yes. Everything lands as plain source in your repository: frontend, backend, admin, database schema. There is no runtime dependency on us and nothing phones home.

Ship in their language.

Start from the free starter, add locale files as your users arrive, and keep every string typed along the way.

Start with the starterSee the CLI

any locale / typed messages / english fallback