Connect Carta to ECA
Give ECA governed access to Carta’s 18 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Carta to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve Carta in Runlayer
Add Carta from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Carta’s 18 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to Carta
Sign in the way Carta requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Carta from ECA
Carta’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
18 Carta tools in ECA
Runlayer policy decides which of these ECA users can call.
Call tool
Run a Carta tool that search_tools found.
Cap table chart
Show a visual cap table summary with ownership breakdown by share class.
Discover
List available Carta commands or views across all domains.
Fetch
Execute a named Carta read command.
Get current user
Get the currently authenticated Carta user's profile.
List accounts
List all companies and organizations the current user has access to.
List contexts
Show which firms you have access to in Carta Fund Admin and which one is currently active.
List resources
List all available resources and resource templates.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Carta call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more