ARCPartner KM OSLaunch partner control plane
Partner registry

Arc ecosystem dossier #99

Tenderly

This partner can be evaluated as a developer tooling / observability participant in Arc's launch and post-launch operating system. The current hard fact is public Arc ecosystem listing; readiness claims need partner-owned or Circle-reviewed evidence.

P1 candidateDeveloper tooling / observabilityneeds review
Arc listing
Fact: listed in Arc's public ecosystem directory.
https://www.arc.io/ecosystem
Dossier status
generated_inventory_dossier
06_partner_dossiers/ecosystem/tenderly.md
Next action
Attach canonical public sources, validate RPC endpoint availability and indexing latency, assign Circle owner, and convert assumptions into reviewed facts.
Launch-Readiness Gates
RPC endpoint availabilityNeeds review

Requires partner-owned source, Circle owner confirmation, or Arcscan/explorer evidence.

indexing latencyNeeds review

Requires partner-owned source, Circle owner confirmation, or Arcscan/explorer evidence.

status/SLA pageNeeds review

Requires partner-owned source, Circle owner confirmation, or Arcscan/explorer evidence.

docs examplesNeeds review

Requires partner-owned source, Circle owner confirmation, or Arcscan/explorer evidence.

incident escalationNeeds review

Requires partner-owned source, Circle owner confirmation, or Arcscan/explorer evidence.

Source Collection Plan
website

Collect facts relevant to readiness, blockers, ownership, support path, and commercial opportunity.

docs

Collect facts relevant to readiness, blockers, ownership, support path, and commercial opportunity.

blog/changelog

Collect facts relevant to readiness, blockers, ownership, support path, and commercial opportunity.

GitHub/releases

Collect facts relevant to readiness, blockers, ownership, support path, and commercial opportunity.

status page

Collect facts relevant to readiness, blockers, ownership, support path, and commercial opportunity.

public API

Collect facts relevant to readiness, blockers, ownership, support path, and commercial opportunity.

Arcscan/explorer

Collect facts relevant to readiness, blockers, ownership, support path, and commercial opportunity.

Public Source Candidates
https://www.arc.io/ecosystemhttps://docs.arc.io/https://testnet.arcscan.app/https://www.google.com/search?q=Tenderly%20docs%20API%20status%20changelog%20RSS%20GitHubhttps://github.com/search?q=Tenderly
Partner Questions
  • - What is Tenderly's canonical product surface for Arc-related integration or support?
  • - Which sources prove readiness, blockers, incidents, or launch milestones?
  • - Who owns this relationship across GTM, product, engineering, and support?
  • - What partner-facing update cadence and escalation SLA should apply?
Evidence Boundary

Fact: Arc publicly lists Tenderly in its ecosystem directory.

Assumption: category, priority, owner, SLA, readiness, and GTM motions need review unless backed by source evidence.

This generated dossier is the starting point for research and source ingestion.