# Telryn

> Maintained provider environments for integration tests, in development.

Telryn is building test environments that reproduce selected external-service behavior for enterprise integration tests. The aim is to reduce mock upkeep and repeated provider investigation. Its planned responsibility is to investigate selected provider behavior, maintain runnable cases and publish their evidence and reviewed corrections. Customers would run the resettable environment alongside their existing connector and application checks.

The homepage uses Salesforce record sync, Microsoft 365 document changes, Slack events and Stripe payment events as illustrative enterprise workflows. They are examples of testing work, not a supported-provider catalogue, partnerships or commitments to deliver those integrations.

## Availability and scope

The product is not yet available. Requesting early access starts a conversation; it does not provide access or reserve a place. SharePoint is the first development focus. Launch timing and commercial terms have not been set.

The initial focus is document-connector teams at software vendors and internal platform teams serving security and classification, search, knowledge products and AI assistants. The first development profile is SharePoint through Microsoft Graph: initial document fetch, additions and updates through polling delta, followed by one selected error case. This is not released provider support. Authentication, deployment compatibility and wider provider fidelity need separate qualification. Additional providers have not been selected.

## Planned responsibilities

Telryn would investigate agreed provider behavior, maintain executable cases and publish reviewed findings and corrections with sources, dates, applicable conditions and known gaps. An investigation could conclude that no change is warranted or evidence is insufficient. Customers would use their existing connector and approved checks, supply minimized test data, configure test endpoints, make application fixes and approve releases.

A local provider container and CLI are in development for customer test environments or CI. They are not released tools. There is no public installation command, supported-provider catalogue or production deployment service. The customer would configure approved test endpoints and authentication, reset application state and run its own assertions. Setup effort must be measured for the connector.

## Evidence and limits

Checking simulator behavior against provider evidence is separate from checking the application. Telryn's planned run check would establish only whether selected provider conditions were exercised. It would not judge application correctness or approve releases. Changes in customer configuration, concurrency, retries or deadlines can require reviewing a case even when the provider API is unchanged. Customers would review and acquire updates explicitly; an offline pinned case cannot certify current provider behavior. A passing application run would cover its recorded conditions, not all customer configurations or every cause of a historical incident. Existing mocks, simulators and sandboxes may already be sufficient. Maintenance savings and recurring demand remain unproven.

The former integration-change and release-control service offers are no longer active. Older offer routes and download URLs lead to the current approach or brief.

## Public pages

- Homepage and early-access request: https://telryn.com/
- Planned approach and current brief: https://telryn.com/approach/
- Early-access brief: https://telryn.com/assets/telryn-early-access-brief.pdf
- Guide library: https://telryn.com/guides/

The featured reading path is:

1. Mocks, Provider Sandboxes or Maintained Test Environments?: https://telryn.com/guides/mocks-sandboxes-maintained-environments/
2. How to Reproduce an Integration Failure in CI: https://telryn.com/guides/reproduce-integration-failure/
3. How to Test Pagination, Rate Limits and Interrupted Syncs: https://telryn.com/guides/test-pagination-rate-limits-interrupted-syncs/
4. How to Keep Integration Tests Trustworthy as Providers Change: https://telryn.com/guides/maintain-integration-checks/

Further reading covers provider changes and migrations. These remain useful technical guides, not Telryn migration-service offers:

- What an API Change Can Break in Your Integration: https://telryn.com/guides/api-change-impact/
- How to Verify an API Migration Across Customer Configurations: https://telryn.com/guides/verify-integration-migration/

Guides contain hypothetical examples, sources and limits. They do not report customer results or demonstrate delivered Telryn capabilities.