Early access

Get notified when Tendryl opens for your team

Leave your email and we'll send your invite when your slot is ready.

Product updates only. Unsubscribe anytime.

Data connectors break at 3am. Ours file their own patches.

Tendryl assigns every connector to an AI agent that owns it outright. The agent writes the connector code, tests it, ships it, watches it run, and rewrites it when the upstream API drifts. You find out in the changelog, not the pager. Rust and RedPanda underneath; finance-grade ticks land in QuestDB for sub-millisecond reads. Built by Colossal Capital × Ackward Roots Inc.

Source on GitHub

// an agent takes ownership of a connector
let agent = Agent::new("binance-ingest")
  .source(BinanceWebSocket::trades("BTCUSDT"))
  .transform(SchemaInfer::auto())
  .sink(RedPanda::topic("crypto.trades.btc"))
  .self_heal(true)
  .deploy();
// the agent monitors, patches, and redeploys from here on

What "self-healing" actually covers

Most pipeline failures are boring and recurring. Those are exactly the ones agents are good at, so we let them handle the loop end to end: detect, rewrite, test against recorded traffic, redeploy.

schema driftA field changes type or disappears upstream. The agent re-infers the schema, adjusts the transform, and backfills what it can.
api changesEndpoint moves, auth flow changes, pagination breaks. The agent reads the failure, patches the client code, and verifies against live responses.
rate limitsBackoff tuned per source, automatically, from observed limit headers and failure patterns.
flapping sourcesReconnect logic with replay from RedPanda offsets, so downstream consumers never see a gap.

From Ackward Roots Inc.

Tendryl is the Colossal Capital × Ackward Roots Inc. shipping product — self-healing connectors on data rails that do not merge the wrong identity. Ackward Roots (founded 2020) is the ideation and hardware lane; see the full research portfolio for climate, identity, LoRa, and twenty other threads.

Incorrect broker records and recycled phone numbers stitch the wrong people together. Charon and Tendryl answer the same failure mode from different layers — identity you own above, honest ingestion below.

Partnership

Ackward Roots holds R&D lineage (including LoRa mesh → Atlas Phone). Colossal Capital operates Hermes, Apollo, and production EKS. Tendryl is where both lanes meet for streaming data.

Sources we connect

family	examples	notes
Exchanges	Binance, Coinbase, Kraken	Trade streams, order-book snapshots, historical backfill.
Blockchains	Ethereum, Polygon, BSC, Cosmos, SUI	Blocks, transactions, contract events, mempool.
Databases	PostgreSQL, MongoDB, Redis, Elasticsearch	CDC, change streams, pub/sub, replication.
APIs	REST, WebSocket, GraphQL, webhooks	Polling and subscriptions with retry and backoff handled for you.

Transforms run on Bento (YAML-declared, 200+ processors) for both batch and streaming. Everything lands in RedPanda first: Kafka-compatible, replayable, millisecond reads. Hot paths for trading and market data are written to QuestDB — column-oriented time-series storage tuned for finance workloads and microsecond ingest latency. InfluxDB is reserved for future IoT projects outside Tendryl; we do not mix sensor telemetry rails with exchange-grade tick data.

Who reads the topics

Tendryl is the ingestion root for the rest of Colossal Capital:

Hermes exposes our RedPanda topics as streaming SQL through Materialize — and serves historical slices from QuestDB when you need tick-level replay.
Versal drives its trading terminal from the price and order-book feeds.
House of Contracts consumes contract events for minting, breeding, and DeFi activity.
Aether indexes NFT mints, sales, and metadata updates.

Connector access is bundled with the platform. Sign up for a Colossal Capital account or check tier details.