Frequently asked questions

GraphJSON is a managed event analytics platform. Your application sends JSON events over HTTP; GraphJSON makes every field available for exploration, dashboards, alerts, ClickHouse SQL, and secure embeds. The five-minute quickstart shows the complete flow.

No. Any language or runtime that can send an HTTP request can log to GraphJSON. We generate ready-to-run snippets for common languages, but the underlying interface is a plain JSON POST. See the logging API reference for the request shape.

Log from your server whenever possible. A browser request would expose your GraphJSON API key to anyone who opens developer tools. If an event originates in the browser, send it through an endpoint you control and let that endpoint add the API key. The browser and mobile collection guide includes a safe first-party proxy pattern.

No. GraphJSON manages event storage, ClickHouse, the query layer, dashboards, and embeds. You send events and decide how long each collection should retain them.

Events ordinarily become available for exploration as they arrive. You do not need to wait for a daily ETL job or rebuild a warehouse model before a new JSON field becomes queryable. GraphJSON does not currently publish a guaranteed maximum ingestion-to-query delay; see service behavior for the operational boundary.

The public ingestion guardrail is 40 requests per second per workspace. The bulk logging endpoint accepts up to 50 events per request, so batching is the correct way to increase event throughput without increasing connection volume. GraphJSON has performed higher internal load tests, but those results do not override the public integration limit. Contact hi@graphjson.com before designing above it.

Yes. Build a graph or dashboard once, then use secure server-generated embed URLs and dynamic filters so each customer sees only their own data. Start with the personalized dashboards guide.

Yes. Published embeds work well for public revenue, usage, or community dashboards. The live metrics walkthrough covers logging the data, building a graph, and placing it on a public page.

Yes. Teams use GraphJSON for product KPIs, operations, revenue, API health, and admin views. Collections can separate workloads by product, environment, or owner, while dashboards bring the important charts back together.

GraphJSON includes integrations for Vercel log drains, Stripe events, and Segment. You can also send data from any other system through the logging API. See the integration guides for setup and security notes. For another provider, use a custom-source adapter that verifies the provider signature, minimizes the payload, and preserves source event IDs.

The free tier includes up to 5,000 stored events. Paid usage is $12 per million stored events per month, based on the highest stored-event watermark recorded during the month. See the pricing page for retention and reads, then use the billing guide for invoices, subscription management, and high-water-mark reconciliation.

GraphJSON uses encrypted connections, server-side API keys, authenticated accounts, and restricted operational access. You control collection retention and can delete collections or export supported Samples, table, and API results. GraphJSON does not currently document a self-service whole-workspace raw archive. Read the security overview, data portability guide, and API key security guide, and shared-responsibility review for details and current assurance boundaries.

GraphJSON does not currently publish an automated public status feed or availability SLA. The service status page explains how to identify and report a possible incident, and the incident guide covers queueing, retry, reconciliation, and safe support metadata.

Email hi@graphjson.com or use the chat button in the product. For implementation questions, the GraphJSON troubleshooting hub routes ingestion, chart, SQL, dashboard, embed, alert, integration, account, and billing symptoms.