Parseable OSS
Self-hosted telemetry data lake for querying logs, metrics and traces stored in columnar files.
16 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Parseable standalone chart migration boundary
Standalone installations using chart 3.0.2 or earlier require a separate 3.1.0+ installation and data migration; the vendor warns against a direct chart upgrade.
Scope: Existing OSS standalone installations through chart 3.0.2; new installations are not affected by this transition.
The guide also distinguishes PVC/temporary staging choices and immutable StatefulSet volume templates.
Action: Create a separate target installation, migrate and verify data, and switch traffic after verification. Follow storage expansion/migration instructions for the selected backend.
Primary source · Reviewed 2026-11-20
What lands where
Supplied by
Vendor or project
Install OSS with Helm in standalone or distributed mode on the documented AWS path, or use the Railway standalone template. Pin application/chart versions and review the migration requirements for older charts.
Runs in
Documented customer environment
Customer-operated standalone server or separate OSS ingestor/querier workloads use local staging and durable object storage for Parquet telemetry.
- AWS: Customer cloud account
- Railway: Customer platform workspace
- AWS
- Railway
Servers / containers
Operated by
Your team
The customer manages credentials, data ingestion, persistent staging, object storage, access configuration, retention, backups and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Parseable OSS on Amazon EKS ↗ · Source checked 2026-11-20
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Parseable OSS on Railway ↗ · Source checked 2026-11-20
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Install OSS with Helm in standalone or distributed mode on the documented AWS path, or use the Railway standalone template. Pin application/chart versions and review the migration requirements for older charts. |
|---|---|
| Infrastructure | Servers / containers Standalone or distributed OSS runs in customer-operated persistent containers/Kubernetes workloads, with durable object storage and staging configured independently. |
| Licensing model | Open Source / Open Core AGPL-3.0 applies to the reviewed OSS release. Official guides cover both standalone and distributed OSS; Enterprise entitlements remain separate. |
| License | AGPL-3.0 for the OSS project. Standalone and distributed OSS deployment guides are available; Enterprise software/support has separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
12 of 12 fields researched (100%) · 6 documented · 6 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery
The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient.
Parseable OSS: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility
No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately.
Parseable OSS: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Parseable OSS supports OIDC sign-in. Configure the issuer, client credentials, redirect URI and OIDC environment for the selected standalone/distributed mode; Parseable roles still control authorization after login. This does not establish SCIM provisioning.
Configured OSS OIDC login; enterprise support and SCIM are separate · Source ↗ · Explicit OSS feature inclusion ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning
The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence.
Parseable OSS: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities.
Parseable OSS: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
OSS documentation provides OIDC authentication, role/privilege controls and API keys. Apply object-store least privilege and protect ingestion/query endpoints. The Railway template uses a moving edge image and a generated admin password when one is not supplied; pin and review the deployed version. Usage-statistics opt-out is separate from identity, storage and optional external integrations.
Configured OSS access controls and deployment credentials · Source ↗ · OSS OIDC configuration ↗ · Railway admin credentials and moving image ↗ · Runtime configuration and telemetry ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation
The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies.
Parseable OSS: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
AvailableEvidence and scope for Deployment artifact / IaC
The inspected Parseable chart 3.2.4 supports OSS standalone and distributed values; its default appVersion is v3.2.3, separate from the reviewed v3.2.7 upstream release. Override an image only after compatibility checks. Standalone chart 3.0.2 or older requires a separate 3.1.0+ installation, verified data migration and traffic cutover rather than an in-place upgrade. The Railway template uses a moving edge image.
Versioned OSS Helm artifact and explicitly moving Railway template · Source ↗ · Deployment artifact ↗ (parseable chart 3.2.4; default appVersion v3.2.3; sha256:02e96d14ca94b55cacb8d30964ee42bf58b3c3add4ecaf571838463c95d8cbdf) · Distributed OSS configuration ↗ · Official Railway template ↗ · Railway image/storage details ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The standalone OSS example requests 250m CPU/1 GiB and limits 500m CPU/4 GiB for the application, with example 5 GiB staging/data volumes depending on storage mode. The distributed example separates ingestors and queriers. These are example requests, not HA throughput minima; object storage, replicated infrastructure and workload capacity are additional.
Vendor example application resources; excludes production HA/database and object-storage sizing · Source ↗ · Distributed OSS topology ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Parseable OSS v3.2.7 uses AGPL-3.0, and the pricing page lists the OSS software tier at $0. Enterprise licensing/support and the customer’s infrastructure and operating labor are separate.
Versioned upstream OSS licence and software-price tier · Source ↗ · OSS pricing and OIDC inclusion ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate
No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend.
Parseable OSS: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The reviewed upstream Parseable OSS snapshot is v3.2.7, published November 17, 2026. Helm chart 3.2.4 defaults to the older v3.2.3 application image, while the Railway template uses edge. Treat application, chart and template versions separately.
Upstream OSS application; packaging defaults and moving templates may lag or differ · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Scope & considerations
The standalone example is a single pod; distributed OSS has a separate vendor guide and is not automatically an HA guarantee. Chart 3.2.4 defaults to application v3.2.3, whereas the reviewed upstream release is v3.2.7. Existing standalone charts through 3.0.2 need a new 3.1.0+ installation and verified data migration. Railway uses a moving edge image, paid Buckets and a persistent staging volume. Disable optional usage statistics with P_SEND_ANONYMOUS_USAGE_DATA=false when required; this alone does not establish air-gapped operation.
Community & maintenance
The upstream project has sustained public contributor history (including nikhilsinhaparseable, nitisht, trueleo) and a reviewed dated v3.2.7 release. This establishes maintenance/community participation rather than a production suitability, support or capacity guarantee.
Category fit
- Observability
- The application ingests and queries operational telemetry and provides dashboards and alerting.
Compare within Observability
- AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
- AWS
- Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
- Google Cloud
- Coroot Community EditionSelf-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- Datadog BYOC LogsDatadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
- AWS
- Azure
- Google Cloud
- Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- AWS
- Azure
- Google Cloud
- Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- AWS
- Azure
- Google Cloud
- Grafana OSS Self-HostedSelf-hosted dashboards, visualization and alerting for operational data.
- AWS
- Langfuse Self-HostedSelf-hosted LLM observability, evaluations and prompt-management platform.
- AWS
- Azure
- Google Cloud
- Railway
- Render
Showing 8 of 20 other listings in Observability. These products address related workflows; read their category-fit notes before comparing scope. See all of Observability →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Parseable OSS source and AGPL-3.0 license ↗github.com
- Standalone OSS Helm installation ↗www.parseable.com
- AWS deployment overview ↗www.parseable.com
- Upstream Parseable releases ↗github.com
- Usage statistics and opt-out ↗www.parseable.com
- Parseable OSS on Amazon EKS ↗www.parseable.com
- Parseable OSS on Railway ↗www.parseable.com
- Distributed OSS configuration ↗www.parseable.com
- Official Railway template ↗railway.com
- Buyer evidence: sso ↗www.parseable.com
- Explicit OSS feature inclusion ↗www.parseable.com
- Buyer evidence: securityControls ↗www.parseable.com
- Runtime configuration and telemetry ↗www.parseable.com
- Buyer evidence: licensePricing ↗github.com
- Buyer evidence: release ↗github.com
- Public contributor history ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Parseable OSS on Amazon EKS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents EKS application hosting and IAM roles for the S3-backed installation. Pair the provider-specific settings with the standalone OSS Helm guide.
- Parseable OSS on Railway ↗ · Railway
Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream template runs the application in the customer's Railway project with a Railway Bucket for durable objects and a persistent volume for staged events.
- Parseable OSS on Amazon EKS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Public contributor history ↗github.com
- Reviewed dated upstream release ↗github.com