Skip to content

Accessibility Statement

Last updated July 11, 2026

Compify is committed to making our website and application usable by as many people as possible, including people who rely on assistive technologies. This statement describes our conformance target, the steps we take, and how to reach us if you hit a barrier.

1. Our commitment

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard referenced by the Americans with Disabilities Act (ADA) and comparable laws. Accessibility is part of how we build and review the product, not an afterthought.

2. Measures we take

  • Semantic HTML with proper landmarks (navigation, main content, footer) and a “skip to content” link on every page.
  • Full keyboard operability, with a visible focus indicator on every interactive element.
  • Text and interface colors chosen to meet WCAG AA contrast ratios.
  • Descriptive text alternatives for meaningful images and icon-only controls.
  • Respect for the operating-system “reduce motion” setting — animations are disabled when you ask for less motion.
  • Responsive layouts that work with zoom and on small screens.

3. Known limitations

Despite our efforts, some content may not yet be fully accessible. Certain data-visualization and animated marketing elements are being reviewed and improved. If you encounter a barrier, please tell us — reports directly shape what we fix next.

4. Feedback and contact

If you have trouble accessing any part of Compify, or want to request information in an alternative format, email accessibility@compify.dev. Please include the page URL and a description of the problem. We aim to respond within five business days.

Ship at lightspeed

Get started freeBook demo

Frequently asked questions

Compify is an MCP gateway that connects AI agents — Claude, ChatGPT, Gemini, Copilot, or any MCP client — to 200+ tools through one URL and one login per vendor. Workflows serialize to versioned YAML specs, so every run is deterministic.

Add your Compify gateway URL as an MCP server in Claude, ChatGPT, or any MCP client, then sign in to each vendor once. Every workflow can then reach those tools, with access scoped per step and credentials reused across runs.

Any client that speaks the Model Context Protocol: Claude (Desktop, Code, and claude.ai), ChatGPT, Gemini, Microsoft Copilot, Perplexity, Ollama, and custom agents you build yourself.

Yes. Both connect AI agents to external tools. Compify focuses on deterministic, versioned workflows you run from any MCP client; Composio focuses on an SDK-first tool catalog for custom agent code. See the full comparison at /compare/compify-vs-composio.

Each workflow serializes to a versioned YAML spec — the same Kit, Connector, and reference set on every run. Same inputs produce the same run, so behavior never drifts between today and next quarter.

A Kit bundles an AI skill with the exact reference docs, images, and examples it needs. The model reads identical context every time, so you never re-explain the task.

Connectors are MCP servers. You bring your own login and OAuth once per vendor — the credential is reused across every workflow, with tool access scoped per step.

Yes. Enterprise plans run the Compify connector gateway inside your own infrastructure with audit logging and scoped access.

No. You compose Kits and Connectors into ordered steps on a visual board. The YAML spec is generated for you and can be edited or version-controlled if you want.