
# Observability on Railway

Compare documented Observability deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/observability/
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.


## Provider guidance

- Account boundary: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### Project networking

Private networking connects services inside a project environment using encrypted tunnels and internal DNS. This project boundary does not give the customer ownership of the underlying infrastructure account.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

The listings below have evidence for Railway. Read each cloud evidence note for the applicable package, edition and support qualifications.

3 listings.


## Langfuse Self-Hosted

Self-hosted LLM observability, evaluations and prompt-management platform.

- Listing: https://launchinyourcloud.com/directory/langfuse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.
- Licensing model: open-source
- Installation: Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.
- Architecture: Application and worker containers with PostgreSQL, ClickHouse, Redis/Valkey and object storage
- Operations: Customer operates the deployment, persistence, access policies, retention, backups and scaling.
- Product website: https://langfuse.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.

The main codebase uses MIT terms outside designated enterprise directories. Enterprise code requires a separate valid license, so the directory treats the combined product as open-core.

The documented deployment uses application/worker containers and persistent database, cache and object-storage services. Host/cluster capacity and database operations remain part of the self-hosted system.


Cloud evidence scope: Documented provider-specific deployment

### Category fit

- ai-observability: LLM/agent tracing, evaluation and prompt management deployed with customer-controlled storage. Evaluation and optional gateway providers must be scoped independently.

- ai-tools: Self-hosted LLM observability, evaluations and prompt-management platform.

- observability: Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/gcp (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/railway (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/render (checked 2026-11-12). 


### Cloud deployment evidence

- Langfuse customer cloud deployment on AWS (aws): https://langfuse.com/self-hosting/deployment/aws
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Azure (azure): https://langfuse.com/self-hosting/deployment/azure
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Google Cloud (gcp): https://langfuse.com/self-hosting/deployment/gcp
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v3 community Railway deployment (railway): https://langfuse.com/self-hosting/deployment/railway
  The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v4 community Render Blueprint (render): https://langfuse.com/self-hosting/deployment/render
  The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker Compose on a VM: https://langfuse.com/self-hosting/deployment/docker-compose

- Self-hosting architecture and provider dependencies: https://langfuse.com/self-hosting

- AWS account Terraform deployment: https://langfuse.com/self-hosting/deployment/aws

- Azure account Terraform deployment: https://langfuse.com/self-hosting/deployment/azure

- Google Cloud account Terraform deployment: https://langfuse.com/self-hosting/deployment/gcp

- Core and enterprise licensing: https://github.com/langfuse/langfuse/blob/main/LICENSE

- Licensing and edition terms: https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

- Langfuse v3 community Railway deployment: https://langfuse.com/self-hosting/deployment/railway

- Langfuse v4 community Render Blueprint: https://langfuse.com/self-hosting/deployment/render

- Langfuse v4.82.0 release: https://github.com/langfuse/langfuse/releases/tag/v4.82.0

### Licensing sources

- https://github.com/langfuse/langfuse/blob/main/LICENSE

- https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

### Infrastructure sources

- https://langfuse.com/self-hosting/deployment/docker-compose

- https://langfuse.com/self-hosting/deployment/aws

- https://langfuse.com/self-hosting/deployment/azure

- https://langfuse.com/self-hosting/deployment/gcp


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted guide documents OAuth/OIDC providers including Keycloak, Okta, Entra ID and a custom issuer. Configure account linking, email verification and access policy; SCIM and separately licensed enterprise features require their own review. Scope: Self-hosted OAuth/OIDC sign-in. Source: https://langfuse.com/self-hosting/security/authentication-and-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose recipe defines application services and backing data services. Pin a compatible Langfuse release and review credentials, persistent storage and exposed ports. Scope: Upstream Compose recipe; supporting-service operations remain customer responsibilities. Source: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The vendor recommends at least 2 CPUs and 4 GB RAM for application containers and at least two Web instances for HA. Worker, ClickHouse, PostgreSQL, Redis and blob storage capacity are additional. Confirm per-container resources and retention/ingestion volume rather than treating this as the whole-stack footprint. Scope: Langfuse Web/Worker resource recommendation; backing services additional. Source: https://langfuse.com/self-hosting/deployment/infrastructure/containers (reviewed 2026-11-20).

- License pricing: Documented. Core code is MIT licensed, while ee directories, including application and worker enterprise paths, use a separate enterprise licence. Optional commercial features and support need separate terms; underlying databases, object storage and model services are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/langfuse/langfuse/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Langfuse v4.82.0 was published November 17, 2026. It fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Scope: Upstream Langfuse self-hosted release. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Langfuse GitHub Enterprise SSO SSRF fix (security-advisory): Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note. Conditions: Requires the affected GitHub Enterprise SSO configuration and a reachable outbound target. Action: Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0; reviewed 2026-11-18.




## OpenSearch

Distributed search and analytics engine with vector retrieval, operational-data analysis and OpenSearch Dashboards visualizations.

- Listing: https://launchinyourcloud.com/directory/opensearch/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream OpenSearch. Separately operated managed services and connected model or data services have their own terms.
- Licensing model: open-source
- Installation: Run official Docker images and customize the documented Docker Compose examples; native package and tarball installations are also documented.
- Architecture: Customer-operated distributed cluster with index shards and replicas on persistent storage, plus optional Dashboards and ingestion components
- Operations: Customer manages cluster sizing, storage, shard and replica layout, TLS, users and roles, ingestion, snapshots, monitoring and upgrades.
- Product website: https://opensearch.org/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Sample deployments and demo security settings require production configuration. Official images distributed through Amazon ECR are not evidence of an AWS-specific deployment. The listing covers self-operated OpenSearch; Amazon OpenSearch Service and other managed services are separate delivery models. Embeddings and AI connectors can involve external models or services. OpenSearch 3.10.0 removes experimental Views and macOS x64 archives and fixes remote-store data-loss or stall paths, bulk-index corruption, heap leaks, snapshot queue stalls, remote-translog issues, and OOM behavior. Validate plugins, Dashboards, and storage recovery before upgrading.

The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms.

Official Docker images run OpenSearch nodes and Dashboards on compatible container hosts. Persistent index storage and host memory and kernel settings are operational requirements; distribution through a cloud registry does not establish a provider deployment badge.


### Category fit

- databases-vector: Indexes and searches vectors alongside metadata, with lexical, nearest-neighbor, semantic and hybrid retrieval. Embedding generation requires an appropriate configured model or externally generated vectors.

- data-analytics: Distributed search and aggregation engine with OpenSearch Dashboards for exploring and visualizing indexed data.

- observability: Search and analytics over ingested operational data, including log analysis and monitoring; collection, ingestion and dashboard configuration remain deployment work.

- ai-tools: Vector storage, semantic search and retrieval for AI applications and RAG. Embedding generation and model connectors have separately configured runtimes and data flows.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/opensearch-analytics (checked 2026-11-12). 


### Cloud deployment evidence

- Self-operated OpenSearch and Dashboards on Railway (railway): https://railway.com/deploy/opensearch-analytics
  The community recipe deploys OpenSearch 3 and Dashboards as customer-project services, with the search API on private networking. Its wrappers derive from upstream OpenSearch images. Review node count, heap/storage sizing, security plugin configuration, TLS and backups; this is separate from Amazon OpenSearch Service and does not imply high availability.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The OpenSearch Software Foundation is organized under the Linux Foundation. Official release records show OpenSearch 3.9.0 released on 29 September 2026 and continuing maintenance planning. Project case studies describe production adoption by Atlassian, LINE and other organizations; managed-service case studies demonstrate project adoption rather than proving self-hosted account boundaries.

Reviewed 2026-11-10.

- OpenSearch Software Foundation: https://opensearch.org/foundation/

- Current releases and maintenance policy: https://opensearch.org/releases/

- Current released artifacts: https://opensearch.org/downloads/

- Named production case studies: https://opensearch.org/case-studies/

### Sources

- OpenSearch Core capabilities and architecture: https://opensearch.org/platform/opensearch-core/

- Vector search documentation: https://docs.opensearch.org/latest/vector-search/

- Official Docker installation: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- Security demo configuration: https://docs.opensearch.org/latest/security/configuration/demo-configuration/

- Release downloads and Apache-2.0 licensing: https://opensearch.org/downloads/

- Upstream Apache-2.0 license: https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

- OpenSearch 3.10.0 release: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0

### Licensing sources

- https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

### Infrastructure sources

- https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- https://opensearch.org/platform/opensearch-core/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The Security plugin supports the SAML 2.0 browser SSO profile, primarily for OpenSearch Dashboards. This is not a general authentication method for every direct OpenSearch client/API call. Scope: OpenSearch Security plugin and Dashboards browser login. Source: https://docs.opensearch.org/latest/security/authentication-backends/saml/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker installation guide provides official images and Compose examples. Configure the required administrator password, persistent data and security settings; demo certificates/settings are not a production security baseline. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide sets a default 1-GB JVM heap and recommends allocating about half of system RAM to heap. It does not establish one complete production minimum: data/index size, roles, replicas, ingestion, Dashboards, vectors and storage performance must be sized separately. A JVM default is not HA capacity. Scope: Upstream JVM/install defaults; full production footprint unresolved. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/index/ (reviewed 2026-11-20).

- License pricing: Documented. The OpenSearch core is Apache-2.0 licensed. Plugins and bundled components require their own licence review; commercial support, managed Amazon OpenSearch Service, model services and infrastructure have separate prices. Scope: Upstream OpenSearch core licence; managed service pricing excluded. Source: https://raw.githubusercontent.com/opensearch-project/OpenSearch/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. OpenSearch 3.10.0 was published November 18, 2026. It removes experimental Views and macOS x64 archives and contains material remote-store, indexing, heap, snapshot, translog, and OOM fixes; match OpenSearch Dashboards and plugins to 3.10. Scope: Upstream OpenSearch 3.10 release. Source: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0 (reviewed 2026-11-18).







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



