Concord Systems

Concord Systems was a Brooklyn, New York stream-processing company founded in December 2014 by Alexander Gallego and Emilio Del Tesoro, and backed by Bloomberg Beta. It built a high-performance distributed stream processing framework written in C++ on top of Apache Mesos, aimed at letting application developers and data scientists write real-time streaming computations ("operators") in the language of their choice — Python, Ruby, Go, Java/Scala, Node.js or Haskell — with Kafka and Amazon Kinesis connectors and a CLI for deploying topologies. Akamai Technologies acquired the company in an all-cash transaction in September 2016 and folded the technology into its IoT edge data platform for real-time messaging and log processing. The company is discontinued: concord.io is parked and the documentation site is gone. Its interface was a Thrift-based operator driver API rather than an HTTP/REST API, so there is no OpenAPI or event surface to catalog; the surviving first-party developer artifacts are the github.com/concord organization and the client libraries still published on PyPI, RubyGems and pkg.go.dev.

Concord Systems is profiled on the APIs.io network. Tagged areas include Company, Stream Processing, Real-Time, Data Processing, and Big Data.

Concord Systems’ developer surface includes CLI and 5 more developer resources.

🌐 Visit website 📡 Source on GitHub

9.3/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0

0 APIs

CompanyStream ProcessingReal-TimeData ProcessingBig DataDistributed SystemsApache MesosKafkaOpen-SourceDiscontinued

Kin Score

Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0

Composite quality — 9.3/100 · minimal

Contract Quality 0.0 / 25

Developer Ergonomics 2.9 / 20

Access Clarity 0.0 / 20

Operational Transparency 0.7 / 13

Contract Governance 0.0 / 12

Discoverability 5.7 / 10

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/concord-systems: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Source (apis.yml)

aid: concord-systems
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/concord-systems.png
name: Concord Systems
description: 'Concord Systems was a Brooklyn, New York stream-processing company founded in December 2014 by Alexander Gallego
  and Emilio Del Tesoro, and backed by Bloomberg Beta. It built a high-performance distributed stream processing framework
  written in C++ on top of Apache Mesos, aimed at letting application developers and data scientists write real-time streaming
  computations ("operators") in the language of their choice — Python, Ruby, Go, Java/Scala, Node.js or Haskell — with Kafka
  and Amazon Kinesis connectors and a CLI for deploying topologies. Akamai Technologies acquired the company in an all-cash
  transaction in September 2016 and folded the technology into its IoT edge data platform for real-time messaging and log
  processing. The company is discontinued: concord.io is parked and the documentation site is gone. Its interface was a Thrift-based
  operator driver API rather than an HTTP/REST API, so there is no OpenAPI or event surface to catalog; the surviving first-party
  developer artifacts are the github.com/concord organization and the client libraries still published on PyPI, RubyGems and
  pkg.go.dev.'
url: https://raw.githubusercontent.com/api-evangelist/concord-systems/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bloomberg-beta
x-tier: stub
x-tier-reason: portfolio-lead
x-status: acquired
x-acquired-by: Akamai Technologies
x-acquired-date: '2016-09-23'
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Stream Processing
- Real-Time
- Data Processing
- Big Data
- Distributed Systems
- Apache Mesos
- Kafka
- Open-Source
- Discontinued
tags_raw:
- Company
- Stream Processing
- Real Time
- Data Processing
- Big Data
- Distributed Systems
- Apache Mesos
- Kafka
- Open Source
- Discontinued
apis: []
common:
- type: GitHubOrganization
  name: GitHub Organization
  url: https://github.com/concord
- type: Packages
  name: Packages
  url: packages/concord-systems-packages.yml
- type: SDKs
  name: SDKs
  url: packages/concord-systems-packages.yml
- type: CLI
  name: CLI
  url: cli/concord-systems-cli.yml
- type: Lifecycle
  name: Lifecycle
  url: lifecycle/concord-systems-lifecycle.yml
- type: LLMsTxt
  name: llms.txt
  url: llms/concord-systems-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 4
  pass: local-v1