← Learn

Quickstart: project & keys

Every playground on this site runs against a shared demo project, so you can explore without an account. To translate your own app you need three things from the Langsys dashboard: a project, a write key, and a read-only key. Two minutes, once.

The setup

1. Sign in at app.langsys.dev — create an account if you don't have one.
2. Create a project. Pick the base locale (the language your source phrases are written in) and the target locales you want translations for. Copy the project id.
3. Mint two API keys for the project: one write key and one read-only key. The split is the whole security model — Keys & environments explains why.
4. Drop them into your env and install the SDK for your stack. Develop with the write key so new phrases register and machine-translate as you build; ship the read-only key.

# .env.local — development (Vite-style names; adjust the prefix to your bundler)
VITE_LANGSYS_PROJECT_ID=your-project-id
VITE_LANGSYS_API_KEY=write-key       # discovers + registers new phrases

# production
VITE_LANGSYS_PROJECT_ID=your-project-id
VITE_LANGSYS_API_KEY=read-only-key   # only fetches — safe to ship in the browser

# .env (Laravel, or your PHP app's environment)
LANGSYS_PROJECT_ID=your-project-id
LANGSYS_API_KEY=write-key            # server-side, so the write key can stay —
                                     # switch to read-only anywhere that must not
                                     # register phrases (e.g. a public sandbox)

Then pick your SDK

Each SDK page starts at Install and assumes exactly this setup — project id and key in your env:

New to the ideas underneath? Start with Concepts — the phrase is the key, token discovery, and the locale store — then come back here.