Run Humlens entirely on your own infrastructure.
Text, image, audio, and video localization — deployed inside your VPC or data center, with your own AI provider keys and no usage caps. Same product. Your data never leaves your network.
$ git clone <video-microservice> ../microservice $ cp .env.selfhost.example .env $ docker compose -f docker-compose.selfhost.yml up -d [+] Running 6/6 ✔ Container humlens-db healthy ✔ Container humlens-redis healthy ✔ Container humlens-migrate exited (0) ✔ Container humlens-app started ✔ Container humlens-video started ✔ Container humlens-video-worker started App is live at https://localise.internal.yourco.com
Same product. Your infrastructure, your keys.
Every capability of the hosted product, deployed inside your own network — with a licensing model built for teams past the point where metered SaaS pricing makes sense.
Your projects, translations, media, and knowledge base never leave your own infrastructure. Run it in your own VPC, your own data center, or air-gapped.
Connect your own Anthropic, OpenAI, or Mistral account for text — the bundled video microservice runs on your OpenAI key too. No per-minute markup, no shared usage caps, no calls to a Humlens-hosted backend.
Text, image, audio, and video localization, AI dubbing and subtitles, knowledge-base-aware translation, glossary enforcement, and QA — the same product as the hosted version.
The ffmpeg-powered transcription, dubbing, subtitle, and image/video localization microservice ships in the same Compose stack, with its own bring-your-own OpenAI key.
A single Docker Compose stack brings up the app, video microservice, Postgres, and Redis, with an optional bundled MinIO for S3-compatible storage. No proprietary orchestration to learn.
SSO/SAML, OIDC, and SCIM directory sync are available as a licensed add-on — connect your existing identity provider and manage access the way the rest of your stack already does.
A licensed audit log module records every admin, AI, export, and publish action — exportable for compliance review, without depending on our hosted infrastructure.
Up and running with one Compose file.
No proprietary orchestration, no vendor-managed control plane — text, image, audio, and video processing all deploy together.
- 1 Clone the video microservice as a sibling directory
One-time setup: check out the ffmpeg video-processing microservice next to the main app repo — the compose file builds it from there.
- 2 Copy the environment template
Set your app URL, database credentials, and your OpenAI key — it powers both the app and the bundled video microservice. Everything else is optional and off by default.
- 3 Bring up the stack
One Docker Compose file: the app, PostgreSQL, Redis, the video microservice, and an optional bundled MinIO if you need S3-compatible storage.
- 4 Point your reverse proxy at it
Terminate TLS in front of the app (and video service, if you use browser-side video features) the same way you already do for everything else in your network.
- 5 License the enterprise module (optional)
Drop in a signed license file to unlock SSO/SAML, SCIM directory sync, and the audit log — no redeploy required.
A flat license, not metered usage.
Self-hosted customers bring their own AI provider keys, so pricing is a flat annual license — not per-minute or per-credit.
Less than Lokalise’s text-only Pro tier — for all four content types, unlimited.
- Unlimited usage — no per-minute or per-credit caps
- Bring your own AI provider keys (Anthropic, OpenAI, Mistral)
- Text, image, audio, and video localization workspaces
- Docker Compose deployment on your own infrastructure
- Standard email support and update access
For organizations that need SSO, directory sync, and audit-ready compliance.
- Everything in Self-Hosted Business
- SSO/SAML, OIDC, and SCIM directory sync
- Full audit log with compliance export
- Priority support with a defined SLA
- Custom contracts and invoicing
Add SSO, directory sync, and audit logging to an existing self-hosted instance.
- SSO/SAML and OIDC via your identity provider
- SCIM directory sync
- Audit log with compliance export
- Licensed independently of usage volume
One flat license beats stacking metered tools.
Lokalise, Rask.ai, and Camb.ai each cover one content type and charge by usage. Humlens self-hosted covers all four, with your own AI keys, for one flat annual license — no per-word, per-minute, or per-credit meter running.
| Lokalise | Rask.ai | Camb.ai | Humlens Self-Hosted | |
|---|---|---|---|---|
| Deployment | Cloud only | Cloud only | Cloud API only | Your own infrastructure |
| Content types | Text / strings only | Video dubbing only | Dubbing & TTS only | Text, image, audio, video |
| Pricing model | Metered by processed words | Metered by minutes ($3/extra min) | Metered by credits | Flat annual license |
| Starting price | $120/mo | $60/mo | $14.99/mo | $500/mo ($6,000/yr) |
| Top published tier | $825/mo (Pro, word-capped) | $750/mo (Business, minute-capped) | ~$10,000/mo (Enterprise, credit-capped) | $14,000–$28,000/yr, unlimited |
| Usage caps | Yes | Yes | Yes | None |
| Bring your own AI keys | No | No | No | Yes |
Competitor figures are publicly listed "starting at" prices as of September 2026 (Lokalise, Rask.ai, Camb.ai official pricing pages) — not custom quotes, and subject to change.
Everything about running Humlens yourself.
- How is self-hosted different from your hosted plans?
- Same application, different infrastructure and cost model. The hosted plans meter usage in credits and minutes because we're paying for AI inference and compute behind the scenes. Self-hosted runs on your own infrastructure with your own AI provider keys, so there's no usage cap — you pay a flat annual license instead of per-minute pricing.
- Do I need my own AI provider account?
- Yes. Self-hosted deployments bring their own Anthropic, OpenAI, and/or Mistral API keys for text workflows. The bundled video microservice (transcription, dubbing, subtitles, image/video localization) runs on your OpenAI key specifically — set it even if your text workflows use a different provider. Either way, you're billed directly by the provider at their rates, not through us.
- What infrastructure do I need to run it?
- A Docker Compose stack brings up the application, the video-processing microservice, PostgreSQL, and Redis, with an optional bundled MinIO for S3-compatible storage if you don't already have a bucket. Put your own reverse proxy in front for TLS. Most teams have it running the same day.
- How does licensing work for SSO, directory sync, and audit log?
- Those three are commercial features, unlocked by a signed license file tied to your deployment. The core localization product underneath is Apache 2.0 and free to self-host on its own — the license only gates the enterprise identity and compliance module.
- Can we start on Self-Hosted Business and add compliance later?
- Yes. The compliance add-on layers onto an existing self-hosted instance without a migration — you'll get a new license file that includes the additional features, and flip the corresponding flags on.
- Is video localization a separate service I have to deploy myself?
- No — the video-processing microservice (transcription, dubbing, subtitles, image/video localization) ships as `video` and `video-worker` services in the same Docker Compose file as the main app. You check it out as a sibling directory once; after that, `docker compose up` brings up both together.
- How does this compare to Lokalise, Rask.ai, or Camb.ai?
- Each of those covers one content type and meters usage: Lokalise is text/strings only, billed by processed words; Rask.ai is video dubbing only, billed by the minute; Camb.ai is dubbing/TTS only, billed by credits. All three are cloud-only — none offer self-hosting. Humlens self-hosted covers text, image, audio, and video in one workspace, runs on your own infrastructure with your own AI keys, and is priced as a flat annual license instead of a usage meter.
Talk to us about your deployment.
Tell us your team size, compliance requirements, and where you need this to run — we'll put together a license that fits.