CONNEX review

The vendor homepage describes IRIS Document Management, including iChannel and Doc.It, rather than a product named CONNEX. Confirm the product identity with the vendor before procurement; the available material does not establish that CONNEX and these IRIS products are the same offering.

Architecturally, the homepage presents a document-management platform for CPA and accounting firms. It centralizes client documents, emails, projects and workflows, and includes client portals for exchanging files. The product sits alongside a firm's accounting and practice-management systems as a place to organize documents and coordinate work. The homepage calls it a connected digital workspace and CRM platform, but does not publish its hosting or deployment model. It is not documented there as a developer library, CLI or self-hosted server. Workflow tracking covers projects, deadlines and team workloads; client portals let clients upload and share files. Treat it as business software, not a programmable service, unless the vendor confirms otherwise.

The homepage describes a user-facing document-management platform, not a developer integration surface. It names no REST API, webhooks, CLI, plugin system, SDK or supported programming language. The integration surface it does describe is general integrations, alongside portals for client document exchange. The feature information also identifies DocuSign integration for sending, signing and tracking agreements. Ask the vendor whether that applies to the product you are evaluating and request the relevant setup documentation.

The homepage links to product support and a Help Hub, but does not identify API reference docs or developer guides. Before planning an integration, ask for documentation covering authentication, available endpoints, events, rate limits, sandbox access and versioning. Confirm SDK support in the vendor's docs rather than assuming a particular language is supported. If your workflow needs automated file ingestion or synchronization with an internal system, get the supported integration method and its operational limits in writing. The published material is not enough to estimate implementation effort.

The pricing information lists no plans or prices, and gives no starting price. It also publishes no monthly or annual billing terms, free trial, usage meter, seat allowance, overage rate or add-on prices. The pricing record indicates no free plan, but its confidence is low, so confirm that directly with the vendor. There is no published figure from which to estimate a production bill.

For a firm-wide document system, request a quote that separates licensing from onboarding, storage, client portal access, integrations and support. Ask whether pricing changes with users, client accounts, document volume or workflow activity, and whether there are charges for data migration or export. Those are questions to resolve, not stated pricing mechanics. If you are comparing this with a usage-priced API, do not assume either a per-request model or a fixed seat price: the vendor's published pricing material provides neither. Get written prices and billing terms for the proposed deployment before budgeting.

The vendor homepage does not publish a source repository or software license, so we cannot classify the product as open source or closed source from that material. It also does not state whether the product can be self-hosted. Do not assume you can run it in your own cloud or data center; ask the vendor to confirm hosting options and any infrastructure requirements.

Data export formats and migration tools are not described. Before committing, ask how to export documents, metadata, client relationships, workflow history and audit records, and whether those exports remain usable outside the product. The platform organizes documents and workflows in one place, so migration may involve more than copying files. Request a sample export and confirm whether configuration and activity history can be transferred. Without those answers, the degree of lock-in is unknown.

The homepage describes secure, branded client portals and centralized document access, but does not publish service-level commitments, availability figures, recovery targets or technical security controls. It also provides no documented rate limits, storage caps, concurrency limits or throughput figures. Do not infer production capacity from feature descriptions; ask the vendor for limits and written service terms for the specific product and plan.

Before relying on the platform, confirm authentication options, encryption, audit logging, retention and deletion behavior, backup and recovery processes, data residency, and any compliance attestations your firm requires. Establish how portal access is revoked and how clients retrieve files at the end of an engagement. If the product connects to practice-management or accounting systems, clarify failure handling and ownership of synchronization errors. The homepage's workflow and portal claims describe intended functions, not measured reliability. Confirm support response times and escalation paths as part of procurement.