generated: '2026-08-30' method: searched source: >- https://www.adaptigent.com/products/core-systems-integration/, https://www.adaptigent.com/resources/pricing/, https://www.adaptigent.com/blog/introducing-adaptive-integration-fabric-v7-2-1/, https://www.adaptigent.com/legal-documents/, https://www.adaptigent.com/terms-of-use/; status/trust subdomain probes (status.adaptigent.com, trust.adaptigent.com — no DNS). description: >- Lifecycle posture for Adaptigent. The company sells installable middleware (Adaptive Integration Fabric, Fabric Data Hub, the Intelligent Caching Engine, NetCOBOL, ASSIST/TS, BMS/TS) rather than operating a hosted API, so the lifecycle signals that normally attach to a public API — a dated API version, a Sunset/Deprecation header policy, a public status page — do not exist here. What does exist is a product release cadence announced on the blog and news feed, and support/maintenance handled through a customer-only portal. versioning: scheme: per-product semantic-style version (major.minor.patch) mechanism: >- Software release version, chosen by the customer at install time. There is no request-level API version header and no server-side version pinning, because the API endpoints the platform produces are generated by and hosted on the customer's own infrastructure. current: Adaptive Integration Fabric: 7.2.1 ASSIST/TS: 9.1.0 BMS/TS: 9.1.0 changelog: changelog/adaptigent-changelog.yml docs: https://www.adaptigent.com/blog/ deprecation: policy_url: null sunset_header: false deprecation_header: false rfc8594: false notes: >- No published deprecation or end-of-life policy was found on the public site. The v7.2.1 release announcement explicitly names no deprecations. Product end-of-support dates, where they exist, are communicated through the customer support portal and contracts, neither of which is publicly readable. No Deprecation pointer is emitted in apis.yml — there is no public policy to point at. sla: url: null public_uptime_target: null notes: >- No public SLA or uptime commitment. Because the runtime is deployed inside the customer's environment (Windows, Linux, or OpenShift Container), availability is the customer's, not Adaptigent's. The one Adaptigent-operated runtime component named publicly is the optional Public Authoritative Count Server (ACS) introduced in Fabric v7.2.0/7.2.1; customers who prefer not to depend on it may run a Private ACS in their own environment. status_page: null status_page_probes: - url: https://status.adaptigent.com/ status: '' - url: https://www.adaptigent.com/status status: 404 support: portal: https://gtsoftware2.zendesk.com/ portal_public: false portal_probe: url: https://gtsoftware2.zendesk.com/api/v2/help_center/en-us/articles.json status: 401 body: '{"error":"Couldn''t authenticate you"}' contact: info@adaptigent.com notes: >- The client portal is a Zendesk instance that redirects to help.gtsoftware.com and answers anonymous browser requests with a Cloudflare interstitial (403); its Help Center API answers 401, which is how a non-public Zendesk help center behaves. Release notes and technical documentation live behind it. deprecated_products: - name: Ivory Suite replaced_by: Adaptive Integration Fabric status: renamed evidence: >- https://www.adaptigent.com/products/ivory-suite/ — "Adaptive Integration Fabric (Formerly Ivory Suite)". A rename and continued line, not a sunset. - name: GT Software replaced_by: Adaptigent status: renamed evidence: https://www.adaptigent.com/news/gt-software-relaunches-as-adaptigent/ maintainers: - FN: Kin Lane X-twitter: apievangelist email: info@apievangelist.com