Managed Langfuse, with the Postgres, ClickHouse and Valkey it needs
Langfuse run for you, together with the PostgreSQL, ClickHouse and Valkey it depends on, in your environment so traces stay with your data.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ: 160+ customers, 10+ years
- ✓24/7 on-call engineers
Langfuse pricing on Langfuse Cloud starts free and rises to $29, $199 and $2,499 a month by plan, billed on traces, observations and scores. Self-hosted Langfuse is free to run but needs a web service, a worker, PostgreSQL, ClickHouse, Redis or Valkey and object storage. OSStend runs that whole stack for you, in your environment.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
What does managed Langfuse from OSStend include?
OSStend runs Langfuse and the data stores underneath it as one managed service: the web and worker services, dedicated PostgreSQL, a dedicated ClickHouse and Valkey, designed for your trace volume and run 24/7 by engineers. The components are the ones Langfuse's own self-hosting page lists.
| Component | What it does (per Langfuse) | With OSStend |
|---|---|---|
| Langfuse Web and Worker | Serves the UI and APIs; processes events asynchronously | Deployed and upgraded for you |
| PostgreSQL | Transactional data | Managed PostgreSQL, run by OSStend. See managed PostgreSQL |
| ClickHouse | Observability data: traces, observations and scores | A dedicated ClickHouse, run by OSStend |
| Redis or Valkey | Caching and job queuing | Managed Valkey. See managed Redis or Valkey |
| S3 or blob storage | Raw events, multi-modal attachments and large exports | Where it lives is settled in the design step |
Source: Langfuse self-hosting overview, checked 17 Nov 2026. OSStend runs the service in your environment, such as your cloud account or your data center.
There is no fixed menu here: the sizes, retention, versions and upgrade dates your workload needs are written into the design you sign off before anything is built, and that design is what OSStend runs.
What does Langfuse pricing look like on Langfuse Cloud?
Langfuse Cloud bills by units: traces, observations (spans, events and generations) and scores. The free Hobby plan includes 50,000 units a month, and paid plans start at $29 a month for 100,000 units, with overage priced per 100,000 units.
| Plan | Price per month | Included units | Data access | Support listed |
|---|---|---|---|---|
| Hobby | Free | 50,000 | 30 days | Community via GitHub |
| Core | $29 | 100,000 | 90 days | In-app support |
| Pro | $199 | 100,000 | 3 years | Prioritized in-app support |
| Enterprise | $2,499 | 100,000 | 3 years | Named support engineer; uptime and support SLAs |
Source: Langfuse pricing, checked 17 Nov 2026. Teams is an add-on to Pro at $300 a month (Pro plus Teams is $499), adding SSO, SSO enforcement, fine-grained RBAC and a dedicated Slack channel. Overage on Core and Pro is $8 per 100,000 units from 100,000 to 1 million, $7 from 1 million to 10 million, $6.50 from 10 million to 50 million and $6 above that. Data retention (permanent deletion after a set period) is a separate feature on Pro and Enterprise.
| Units in a month | Core plan at list rates |
|---|---|
| 200,000 | $37 |
| 1 million | $101 |
| 10 million | $731 |
Arithmetic from the Core base and overage rates on Langfuse pricing, checked 17 Nov 2026, not a quote. Each row is $29 plus the overage tiers it passes through.
Langfuse Cloud is hosted by Langfuse. If trace data has to stay in your own cloud account or data center, the alternative is to self-host.
What does self-hosted Langfuse need?
Self-hosted Langfuse needs six parts, and the free price covers only the software. Langfuse's own page lists the web service, worker, PostgreSQL, ClickHouse, Redis or Valkey and S3 or blob storage, and says Docker Compose is for local use and testing.
- Langfuse describes Docker Compose as a single VM "without high availability, scaling, or backups". Production options it lists are Kubernetes (Helm) and deployments on AWS, Azure and GCP (Langfuse self-hosting, checked 17 Nov 2026).
- The repository is MIT licensed except for the `ee` folders, and the self-hosting page says some add-on features need a license key (GitHub, self-hosting, checked 17 Nov 2026). Check which features you need before the design is signed off.
- ClickHouse and PostgreSQL are the parts that grow and fail in ways Docker Compose does not cover: backups, replication, upgrades and disk growth are all yours when you self-host.
For where Langfuse sits among the other data services behind a private LLM, see self-hosted AI: the data layer.
From our on-call engineers: the Redis and storage settings Langfuse depends on
Langfuse's failure modes live in its queue and its blob storage. The settings below are the ones its documentation marks as required, and the ones we check first when traces go missing.
- ✓Redis must have maxmemory-policy set to noeviction so queue jobs are not evicted, and the setting applies to all cluster nodes and to Sentinel primary and replicas.
- ✓The documented minimum is Redis 7 or Valkey 8, and the Redis user needs access to all keys and commands (on ~* +@all).
- ✓Use the default Redis database number, since some managed Redis products do not allow a nonzero database.
- ✓Events are written to S3 or blob storage first and to the database only after successful processing, so the blob bucket is part of the durability path and needs its own retention and access policy.
- ✓Traces and scores live in ClickHouse and transactional data in Postgres, so a backup plan covers both stores plus the bucket.
Langfuse Cloud, self-hosted or managed by OSStend?
Langfuse Cloud costs least to start, self-hosting keeps data in your environment, and OSStend gives you self-hosted control without your team carrying the pager. The right one depends on where trace data may live and who is on call.
| Factor | OSStend | Langfuse Cloud | Self-hosted yourself |
|---|---|---|---|
| Who runs it | OSStend engineers, 24/7 | Langfuse | Your team |
| Where trace data lives | Langfuse and its stores in your environment, such as your cloud account or your data center | Langfuse Cloud | Wherever you deploy it |
| Pricing | Quoted per design. See pricing | Free, $29, $199, $2,499 a month by plan, plus unit overage (Langfuse pricing) | Software is free; you pay for the infrastructure and the people |
| Databases | PostgreSQL, ClickHouse and Valkey run for you | Run by Langfuse | You run all of them |
| Good fit | Trace data must stay in your environment and nobody wants to operate ClickHouse | Small teams, fast start, no residency constraint | A platform team already running ClickHouse and PostgreSQL |
| Poor fit | A free tier or a card sign-up | Data that cannot leave your environment | No one to carry the pager |
How we compared: Langfuse's own pricing and self-hosting pages, checked 17 Nov 2026. The OSStend column describes the service; its price is set after a workload review.
How does moving to managed Langfuse work?
The new stack is built beside your current Langfuse and verified before anything switches. The first step is a 45-minute workload review with an engineer: the current setup is reviewed, the design is sketched, and a price follows for that design.
Review
An engineer reviews the current setup: sizes, settings, modules or plugins, versions, traffic and where it must run.
Design
The cluster design is written and signed off before anything is built: size, topology, configs, versions and upgrade calendar.
Move
The new cluster runs beside the old one and stays current while the old service stays live. Traffic switches only when the new side is verified.
Run
Named engineers operate it 24/7: backups, patching, scaling and incident response, with upgrades on the customer's change calendar.
Questions about Langfuse pricing and hosting
These are the questions teams ask when they compare Langfuse Cloud with running it themselves.
How much does Langfuse cost?
Langfuse Cloud lists a free Hobby plan, then Core at $29, Pro at $199 and Enterprise at $2,499 a month, with usage billed per 100,000 units above the included 100,000 (Langfuse pricing, checked 17 Nov 2026). Self-hosting the software is free.
What does self-hosted Langfuse need to run?
A web service, a worker, PostgreSQL, ClickHouse, Redis or Valkey and S3 or blob storage (Langfuse self-hosting, checked 17 Nov 2026). OSStend runs that stack for you.
Can OSStend run Langfuse in my own cloud account?
Yes. OSStend runs it in your environment, such as your cloud account or your data center, to a design you sign off before anything is built.
Is self-hosted Langfuse the same as Langfuse Cloud?
Mostly the same software. Langfuse notes that some add-on features need a license key and that features marked EE are Enterprise Edition (Langfuse self-hosting, checked 17 Nov 2026). Confirm the features you need before choosing.
When is Langfuse Cloud the better choice?
When you want the fastest start, have no data residency requirement, or the volume sits inside the free or Core plan. A managed stack is for data that has to stay in your environment.
Related pages
- PostgreSQLManaged PostgreSQL service and Postgres hostingManaged PostgreSQL service, compared: how to choose between RDS, Aiven, Crunchy Bridge, Neon and a tailored cluster run 24/7 in your cloud or ours.
- Redis or ValkeyManaged Redis or Valkey, your choice of engineManaged Redis or Valkey: you choose the engine, with persistence, eviction and configuration set for your workload, run 24/7 in your cloud or data center.
- GuideSelf-hosted AI: the data layer for a private LLMRunning AI on your own infrastructure: which data services a private LLM needs (vectors, cache, memory, events, tracing) and how to run them in production.
- PricingDatabase as a service pricing: dedicated, tailoredDatabase as a service pricing from OSStend: dedicated, tailored clusters priced by engine, size, SLA tier and location. Enterprise only, with no free tier.
Talk to an engineer about Langfuse
45 minutes: bring your trace volume and where the data must live, and the engineer sketches the Langfuse stack.
- ✓A design sketch for your workload, not a plan menu
- ✓A zero-downtime cutover path for what you run today
- ✓A price for that design, after the review