Known differences
Each Era system answers its vendor's own API, and each one differs from the vendor somewhere. These pages list, per system, what is supported, what is not, and every recorded difference with what a test should and should not assert against the replica. Each entry is read from the system's code, README or tests.
| System | Surfaces | Supported | Not supported | Differences |
|---|---|---|---|---|
| GitHub | Git, GraphQL, MCP, REST, Webhooks | 6 | 2 | 6 |
| Gong | MCP, OAuth, REST | 4 | 2 | 6 |
| Google Drive | MCP, OAuth, REST | 6 | 4 | 7 |
| HubSpot | MCP, OAuth, REST, Webhooks | 5 | 1 | 4 |
| Jira and Confluence | MCP, REST | 6 | 5 | 6 |
| Notion | MCP, OAuth, REST, Webhooks | 6 | 4 | 6 |
| Salesforce | GraphQL, MCP, OAuth, REST, SOAP, Streaming, gRPC | 7 | 6 | 8 |
| ServiceNow | MCP, OAuth, REST | 7 | 2 | 5 |
| Slack | MCP, OAuth, REST, Streaming, Webhooks | 6 | 3 | 8 |
| Zendesk | MCP, REST, Webhooks | 6 | 5 | 6 |
Applies to every system
- The hosted data plane is read-only: a write is refused with
403 writes_disabled. A SOQL, GraphQL or searchPOSTis a read and is answered. - Faults are injected through
POST /_admin/faultson a simulator you run yourself;POST /_admin/faults/resetclears them. - Rate limits do not happen on their own unless a page says so. Use fault injection to exercise a client's backoff.
- Distributions come from aggregated metadata sketches of data Eon backs up; no customer records; all Era data is simulated.