EARLY ACCESSEVENT MESH RUNTIME v1.0 • SOC 2 TYPE II IN PROGRESS
Route high-volume event streams across regions without broker bottlenecks.
FlintMesh gives platform teams a deterministic, schema-enforced event mesh that ingests webhook, Kafka, and gRPC payloads at the edge and fans them out across regions with sub-10ms edge routing.
Stream device readings over gRPC, filter with CEL at the edge, and alert on threshold breaches.
iot.telemetry → CEL filter → cold-chain alerts
Auth & audit events
Route session and login events to SIEM and analytics with region pinning for data residency.
auth.session → residency: eu → SIEM, analytics
Architecture
Validate at the edge. Fan out in memory. Never park data on disk.
Every FlintMesh point of presence runs the same stateless ingress node: decode, enforce schema, evaluate routing rules, then replicate across the peered mesh. Brokers, partitions, and rebalances stop being your problem.
Deterministic Schema Guard
Reject malformed payloads at the ingress edge using JSON Schema or Protobuf before they pollute downstream consumers.
From npm install to first fan-out in four minutes.
Typed SDKs for TypeScript and Go, with more languages planned. Every client speaks the same wire protocol, so producers and workers can be mixed freely across languages and clouds.
Provision a sandbox
Request a cluster below or run flint auth login to bind the CLI to your workspace.
Register a schema
Push JSON Schema or .proto files; the edge rejects anything that doesn't match.
Publish & subscribe
Producers publish to topics; workers subscribe with consumer groups and automatic acks.
Ship routing rules
Commit CEL routes and apply with flint apply -f mesh.yaml from CI.
src/publish.tsTypeScript
Security
Built for the vendor review, not around it.
Payloads move through memory, encrypted in transit, and are only written to disk inside your replay vault — with keys you can hold yourself.
In progress
SOC 2 Type II
SOC 2 Type II in progress on a security-first architecture; our security questionnaire is available on request.
Enforced
mTLS everywhere
TLS 1.3 at ingress and mutual TLS between every mesh node, with automatic certificate rotation.
Optional
Customer-managed keys
Replay vault encrypted with AES-256-GCM using your AWS KMS, GCP KMS, or Azure Key Vault keys.
Default
Data residency
Pin topics to EU or US regions; routing rules can never forward pinned events outside them.
Need the full control list, sub-processors, or a DPA?
Pricing
Usage-based. Published. No sales call to see a number.
Pay for events delivered, not for brokers idling at 4 a.m. Every tier includes the full schema guard, CEL routing, and the CLI.
Effective November 18, 2026 · FlintMesh Systems Inc.
1. Who we are
FlintMesh Systems Inc. ("FlintMesh", "we") is a Delaware corporation located at 1007 N Orange St, 4th Floor, Suite 1382, Wilmington, DE 19801, United States. We operate flintmesh.dev and the FlintMesh event mesh service.
2. Information we collect
Account data: work email, company name, billing contact, and the volume and cloud preferences you submit.
Service telemetry: event counts, latency, error rates, and routing metadata needed to operate and bill the service.
Website data: basic server logs (IP address, user agent, timestamps) kept for security for up to 30 days.
3. Customer event payloads
Event payloads you route through FlintMesh are processed on your behalf as a processor. They transit in memory and are only persisted inside your encrypted replay vault for the retention window you configure (maximum 14 days on standard plans). We do not inspect, sell, or use payload contents to train models.
4. How we use information
To provision and operate your clusters, provide support, send service and billing notices, detect abuse, and meet legal obligations. Marketing email is opt-in and can be stopped at any time.
5. Sharing
We share data only with sub-processors needed to run the service (cloud infrastructure, payment processing, support tooling), each bound by a written data processing agreement. A current list is available on request.
6. Your rights
You may request access, correction, export, or deletion of your personal data. EU/UK customers may rely on our Standard Contractual Clauses. Contact support@flintmesh.dev.
Effective November 18, 2026 · FlintMesh Systems Inc.
1. Agreement
These Terms govern your use of the FlintMesh service and flintmesh.dev, provided by FlintMesh Systems Inc., 1007 N Orange St, 4th Floor, Suite 1382, Wilmington, DE 19801. By creating a sandbox or account you accept them on behalf of your organization.
2. The service
FlintMesh provides managed event ingestion, schema validation, routing, replay, and fan-out across regions. Sandbox clusters are provided as-is for evaluation and expire after 30 days unless upgraded.
3. Fees
Paid plans are billed monthly in advance for the base fee and in arrears for usage above included volume, at the rates published on our pricing page. Enterprise terms are set in an order form.
4. Acceptable use
You will not use the service to transmit unlawful content, attack other systems, or attempt to circumvent usage limits or tenant isolation.
5. Your data
You retain all rights to the event data you route. You grant FlintMesh a limited license to process it solely to provide the service.
6. Service levels
Production Mesh runs with multi-region high availability and automated failover. Dedicated Enterprise customers may agree a custom SLA, with any service credits set out in their order form.
7. Liability
Except for breaches of confidentiality or indemnity obligations, each party's aggregate liability is limited to the fees paid in the twelve months preceding the claim.
8. Governing law
These Terms are governed by the laws of the State of Delaware. Questions: support@flintmesh.dev.
Last reviewed November 2026 · security contact nolan@flintmesh.dev
Compliance program
SOC 2 Type II — in progress. The platform follows a security-first architecture from day one.
GDPR-ready Data Processing Agreement with Standard Contractual Clauses.
Security questionnaire and architecture overview available on request.
Encryption
TLS 1.3 at every ingress point and mutual TLS between mesh nodes. Replay vault data is encrypted with AES-256-GCM; Enterprise customers may supply their own KMS keys.
Data handling
The routing hot path is memory-only: no payload is written to disk outside the encrypted replay vault, which expires automatically at the end of its retention window.
Network isolation
Private connectivity via AWS PrivateLink, GCP Private Service Connect, and VPC peering. Dedicated Enterprise runs on single-tenant bare-metal nodes or in your own cloud account.
Access control
SSO (SAML/OIDC), SCIM provisioning, scoped API keys, and an immutable audit log of every configuration change.
Responsible disclosure
Report vulnerabilities to support@flintmesh.dev with "Security disclosure" in the subject. We acknowledge reports within one business day.