Introduction
What Nexra is, how its parts fit together and where to start.
Updated 09/10/2026
On this page
What Nexra does
Nexra is an integration platform. It connects the business systems your teams already use (ERP, accounting, payments, commerce, CRM, HR, support, project management, data warehouses and AI services) and moves data between them through governed flows that people can review, approve and monitor.
Nexra has two layers. Nexra Connect is the integration platform as a service (iPaaS): connect accounts, map fields and run flows without an agent. The agentic control layer adds capability discovery, policies, approvals, checks, monitoring and evidence over those same connections. Customers can bring an MCP client, use Nexra Agent in the console, or call the Gateway API from their own backend. Access is bounded by workspace membership and, for Gateway/MCP credentials, the application's project and grants.
An implemented adapter, a successful connection test and a completed workflow are different levels of evidence. Check the connector's recorded validation level and qualify your exact operation and account before relying on it. Client compatibility does not establish a completed client journey. Configure a release gate on each integration that must pass checks before promotion; the existence of checks does not make them mandatory on every integration. Evidence can be verified and exported by authorised workspace members.
| Part | What it is for |
|---|---|
| Nexra Connect | Implemented provider adapters and private REST/OpenAPI connections, flows that read from one system and write to another, field mappings, schedules, approvals, run history and recovery. |
| Govern | Risk tiers, policies, amount limits, grants and approvals bound to the exact action, for every write a flow or agent makes. |
| Prove | A hash-chained evidence trail you can verify and export, checks and release gates, and a signed audit log. |
| MCP | A hosted Model Context Protocol server, so AI agents can read your APIs and docs and trigger approved Connect flows. |
| Developer portal | Applications, sandbox keys, the API explorer, webhooks, usage and request logs. |
| Developer tools | Generated SDKs, downloadable OpenAPI and Postman artefacts, and a command-line client (preview). |
| Documentation workspace | Author, review and publish documentation pages, and keep a changelog. |
How a typical integration comes together
Create a project in your workspace. Projects group connections, integrations and applications.
Connect each system. Credentials are stored in a secure vault; Nexra keeps only a reference.
Build an integration with one or more flows: a trigger, a source operation, mappings and a destination operation.
Test in sandbox with mapping previews, then publish the flow version.
Request a production deployment. A second person approves it before it can run.
Monitor runs, retry failed records from the dead-letter queue, and expose the integration to agents over MCP or export its service contract.
Environments
Sandbox and production are isolated. Connections, flow versions, credentials, webhooks and logs belong to one environment. Production runs need an approved deployment, and production API access for an application needs an approved readiness review.
Hosts
| Purpose | URL |
|---|---|
| Developer portal and console | https://developer.amakoragroup.com |
| Your API base URL | https://api.nexra.amakoragroup.com |
| MCP endpoint | https://api.nexra.amakoragroup.com/mcp |
Where to go next
Quickstart: from sign-up to a first sandbox request and a first Connect flow.
Connect overview: connections, flows and the run lifecycle.
Govern overview: decide which writes run, wait for a person or are refused.
Prove overview: verify and export the evidence of every action.
Use the Nexra MCP server: connect an AI agent.
API overview: base URL, authentication, errors and limits for the platform API.
Connector directory: every provider with its operations, limits and restrictions.