eCAP is a content adaptation interface for web applications. It allows host applications such as HTTP proxies and ICAP servers to outsource message analysis and rewriting to loadable modules. It is similar to an “embedded ICAP”: network interactions with an ICAP server are replaced by function calls to adaptation modules. The host passes protocol message details to the module, and the module can return a rewritten message, decline to process it, or immediately issue a blocking instruction. It can also exchange metadata such as configuration, virus names, and reasons for ignoring content.
In terms of functionality, eCAP covers typical gateway use cases such as logging, filtering, blocking, injection, translation, decoding, encoding, and virus scanning. libecap implements the API in C++, but the library itself mainly declares interfaces; the actual logic is implemented by the host and adapters. Adapter development requires implementing adapter::Service and adapter::Xaction, while host integration requires implementing host::Host, host::Xaction, and MIME-like message wrappers, which is more challenging. The main documentation clearly provides a Squid integration example and also mentions the Spicer ICAP server, indicating that its ecosystem is more focused on low-level proxy, caching, and security gateway infrastructure.
No commercial pricing or paid plans are mentioned in the main text. The site provides an open-source implementation, libecap, sample adapters, and an AV SDK. Deployment follows the traditional Unix-like source compilation workflow: configure, make, make install, then enable --enable-ecap in Squid and configure loadable_modules, ecap_service, and related settings. It is not a SaaS product, but a local component intended to be embedded into your own infrastructure.
The main advantage is its clear interface boundary, which decouples the host application from the specific content-processing logic. Once an adapter is implemented according to the standard interface, it can theoretically run in any eCAP-enabled application. The sample configuration is also fairly concrete, which helps with validation. The drawbacks are also obvious: the documentation is described as “partial detailed documentation,” and browsable documentation is still planned; APIs and source code in early versions may change; the sample adapters are not suitable for production and do not handle compressed content. A production-grade implementation would need additional work around performance, compression, threading, and non-blocking scanning.
eCAP is suitable for teams with experience in C++, HTTP proxies, Squid/ICAP, or security gateways, especially for developing modules for content filtering, response injection, antivirus scanning, and enterprise proxy auditing. It is not suitable for low-code users who want something ready to use out of the box. There is no verifiable information in the main text about access from China, so it should be considered unknown; there is also no payment-related information. If your team is more familiar with standard network protocols, you may want to evaluate ICAP/RFC 3507 or Squid-related content adaptation solutions as alternatives.
⚠ This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on e-cap.org official site.
e-cap.org is an Unknown Dev Tools provider. TG4G tracks its product information, an overall rating of 6.0/10, and a China-accessibility score of China direct-connect friendly. Click "Visit Official Site" to reach e-cap.org directly.