Platform overview

StringPush separates who edits copy from how your app loads it.

Core objects

Term	Meaning
Organization	Your team account (billing, members, SSO).
Project	One product’s translation catalog (keys, locales, publish history).
Application	One frontend install — has its own runtime API key and allowed domains.
Key	Stable id for a message, e.g. checkout.pay or common.greeting.
Locale	BCP 47 tag, e.g. en, de-DE.
Environment	staging or production — separate bundle streams.

Runtime flow

flowchart LR
  App[Your app init]
  API[API manifest]
  CDN[CDN bundle JSON]
  App --> API
  App --> CDN
  App --> t["t(key, values)"]

1. Your app calls init() with a runtime API key (read-only, safe in the browser).
2. The SDK fetches a small manifest from the API.
3. The SDK loads immutable bundle JSON from the CDN for the active locale.
4. You call t('key') or t('key', { name: 'Ada' }) at render time.

Staging vs production

	Staging	Production
Purpose	QA, overlay editing, pre-release copy	Live user traffic
Overlay	Enabled by default	Off unless org enables it
Publish	Publish staging in admin	Promote staging → production

See Manifest & bundles and Keys & namespaces.