Unified search
Search entries, examples, grammar features, constructions, and admin directives without leaving the main workspace.
Language work, owned by you
A self-hosted home for dictionaries, grammar notes, examples, and language teams.
Langnerd keeps your language data on your own server while giving contributors a fast, searchable interface for lexicons, phonology, morphology, and proposals.
#entry water
noun
ama
water; river water; drinkable water
2 examples · 4 revisions · proposed by Mira
directive
#members
Invite contributors, review roles, and keep access local to your instance.
Built for living languages
Lexicon, grammar, and collaboration in one searchable place.
Self-hosted
Run Langnerd on your server with SQLite for small teams or Postgres when your community grows.
Revision-aware
Track proposals, lexical history, generated forms, markers, and morphology rules as the language evolves.
Contributor friendly
Invite members, review contributions, and keep project settings inside focused directive cards.
Pricing
Use the free self-hosted app, upgrade when your team needs more.
Pro licenses are account-bound and activate your self-hosted instance without sending your language data to Langnerd.
Free
$0
For personal projects, prototypes, and local language notes.
- Self-hosted app
- SQLite or Postgres
- No license key required
Most teams
Pro Monthly
$5 / month
For active teams maintaining shared language resources.
- Account-bound activation
- Automatic license refresh
- Supports team and public-language limits
Save $10
Pro Yearly
$50 / year
Same Pro license, paid yearly.
- Two months included
- Account-bound activation
- Cancel from Stripe billing
FAQ
Questions before you host it?
Does Langnerd host my language data?
No. The app is self-hosted. The licensing service only tracks account, subscription, and instance activation metadata.
Can I use it without paying?
Yes. The free tier requires no key. Paid licenses unlock Pro limits and subscription-backed activation.
What database should I use?
Use SQLite for a simple single-server setup. Use Postgres when you want a more production-oriented deployment.