
# Parseable OSS

Self-hosted telemetry data lake for querying logs, metrics and traces stored in columnar files.

Canonical page: https://launchinyourcloud.com/directory/parseable-oss/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Parseable OSS

Self-hosted telemetry data lake for querying logs, metrics and traces stored in columnar files.

- Listing: https://launchinyourcloud.com/directory/parseable-oss/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 for the OSS project. Standalone and distributed OSS deployment guides are available; Enterprise software/support has separate terms.
- Licensing model: open-source
- Installation: 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.
- Architecture: Customer-operated standalone server or separate OSS ingestor/querier workloads use local staging and durable object storage for Parquet telemetry.
- Operations: The customer manages credentials, data ingestion, persistent staging, object storage, access configuration, retention, backups and upgrades.
- Product website: https://www.parseable.com/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

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.

AGPL-3.0 applies to the reviewed OSS release. Official guides cover both standalone and distributed OSS; Enterprise entitlements remain separate.

Standalone or distributed OSS runs in customer-operated persistent containers/Kubernetes workloads, with durable object storage and staging configured independently.


### Category fit

- observability: The application ingests and queries operational telemetry and provides dashboards and alerting.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/aws-eks (checked 2026-11-20). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/railway (checked 2026-11-20). 


### Cloud deployment evidence

- Parseable OSS on Amazon EKS (aws): https://www.parseable.com/docs/self-hosted/installation/standalone/aws-eks
  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.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Parseable OSS on Railway (railway): https://www.parseable.com/docs/self-hosted/installation/standalone/railway
  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.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-20.

- Public contributor history: https://github.com/parseablehq/parseable/graphs/contributors

- Reviewed dated upstream release: https://github.com/parseablehq/parseable/releases/tag/v3.2.7

### Sources

- Parseable OSS source and AGPL-3.0 license: https://github.com/parseablehq/parseable

- Standalone OSS Helm installation: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss

- AWS deployment overview: https://www.parseable.com/docs/self-hosted/aws

- Upstream Parseable releases: https://github.com/parseablehq/parseable/releases

- Usage statistics and opt-out: https://www.parseable.com/docs/self-hosted/telemetry

- Parseable OSS on Amazon EKS: https://www.parseable.com/docs/self-hosted/installation/standalone/aws-eks

- Parseable OSS on Railway: https://www.parseable.com/docs/self-hosted/installation/standalone/railway

- Distributed OSS configuration: https://www.parseable.com/docs/self-hosted/installation/distributed/k8s-helm-oss

- Official Railway template: https://railway.com/deploy/parseable-1

- Buyer evidence: sso: https://www.parseable.com/docs/user-guide/openid

- Explicit OSS feature inclusion: https://www.parseable.com/pricing

- Buyer evidence: securityControls: https://www.parseable.com/docs/user-guide/rbac

- Runtime configuration and telemetry: https://www.parseable.com/docs/self-hosted/configuration

- Buyer evidence: licensePricing: https://github.com/parseablehq/parseable/blob/v3.2.7/LICENSE

- Buyer evidence: release: https://github.com/parseablehq/parseable/releases/tag/v3.2.7

- Public contributor history: https://github.com/parseablehq/parseable/graphs/contributors

### Licensing sources

- https://github.com/parseablehq/parseable

- https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss

### Infrastructure sources

- https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss

- https://www.parseable.com/docs/self-hosted/installation/standalone/railway


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. 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. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Single sign-on: Documented. 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. Scope: Configured OSS OIDC login; enterprise support and SCIM are separate. Source: https://www.parseable.com/docs/user-guide/openid (reviewed 2026-11-20). Supporting source: Explicit OSS feature inclusion — https://www.parseable.com/pricing.

- SCIM provisioning: Sources checked — unresolved. 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. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. 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. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Security controls: Documented. 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. Scope: Configured OSS access controls and deployment credentials. Source: https://www.parseable.com/docs/user-guide/rbac (reviewed 2026-11-20). Supporting source: OSS OIDC configuration — https://www.parseable.com/docs/user-guide/openid. Supporting source: Railway admin credentials and moving image — https://www.parseable.com/docs/self-hosted/installation/standalone/railway. Supporting source: Runtime configuration and telemetry — https://www.parseable.com/docs/self-hosted/configuration.

- Air-gapped operation: Sources checked — unresolved. 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. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. 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. Scope: Versioned OSS Helm artifact and explicitly moving Railway template. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss (reviewed 2026-11-20). Deployment artifact: https://charts.parseable.com/helm-releases/parseable-3.2.4.tgz. Artifact reference: parseable chart 3.2.4; default appVersion v3.2.3; sha256:02e96d14ca94b55cacb8d30964ee42bf58b3c3add4ecaf571838463c95d8cbdf. Supporting source: Distributed OSS configuration — https://www.parseable.com/docs/self-hosted/installation/distributed/k8s-helm-oss. Supporting source: Official Railway template — https://railway.com/deploy/parseable-1. Supporting source: Railway image/storage details — https://www.parseable.com/docs/self-hosted/installation/standalone/railway.

- Minimum footprint / sizing: Documented. 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. Scope: Vendor example application resources; excludes production HA/database and object-storage sizing. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss (reviewed 2026-11-20). Supporting source: Distributed OSS topology — https://www.parseable.com/docs/self-hosted/installation/distributed/k8s-helm-oss.

- License pricing: Documented. 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. Scope: Versioned upstream OSS licence and software-price tier. Source: https://github.com/parseablehq/parseable/blob/v3.2.7/LICENSE (reviewed 2026-11-20). Supporting source: OSS pricing and OIDC inclusion — https://www.parseable.com/pricing.

- Operating cost estimate: Sources checked — unresolved. 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. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. 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. Scope: Upstream OSS application; packaging defaults and moving templates may lag or differ. Source: https://github.com/parseablehq/parseable/releases/tag/v3.2.7 (reviewed 2026-11-20).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Parseable standalone chart migration boundary (lifecycle): 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. Conditions: 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. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss; reviewed 2026-11-20.



