nexos.ai vs Portkey (2026)

Workspace Integrations reach Google Drive, Mail and Calendar and Microsoft Outlook, OneDrive, SharePoint, Teams and Calendar on the productivity side, Atlassian, GitHub and GitLab through their MCP servers, and Slack, HiBob, Looker, Google Ads and BigQuery. Organization admins activate them and each user connects through the provider's own sign in. Agents take write actions through these integrations, such as sending a message, creating a ticket or updating a record.

Sourcedocs.nexos.ai/workspace/integrationsread 2026-09-22

Agents authenticate once to Portkey's MCP Gateway, which sits between them and MCP servers. For each tool call, the gateway checks that user's access to the server and tool, then injects the upstream credentials (OAuth, API keys or custom headers, with external identity providers such as Okta and Auth0). Servers and individual tools are provisioned per workspace and user. Through the gateway, agents take authenticated action in outside systems.

Sourcedocs.portkey.ai/docs/product/mcp-gatewayread 2026-09-22

A visual Flow in Agent Builder shows the steps an agent will take to complete its task, with optional human in the loop review steps, and agents run multi step work across connected tools on demand or on a schedule. There are no deterministic nodes, branching or multi agent handoff.

Sourcedocs.nexos.ai/workspace/agents/agent-builderread 2026-09-22

The Agent Gateway is a proxy between agent clients and the customer's own agent servers. It handles authentication, access control and observability for registered A2A agents, and the agents and their steps run on the customer's servers. Portkey has no workflow definitions and runs no agents of its own, so nothing in it sequences or branches agent steps.

Sourcedocs.portkey.ai/docs/product/agent-gatewayread 2026-09-22

A schedule can be set on an agent (hourly, daily, monthly or yearly), so it runs automatically in the background. Agents can run periodically, for example to produce a morning summary of Slack updates, and scheduled runs appear in the agent's Activity history. Agents are also reachable from Slack, Microsoft Teams, Telegram and WhatsApp.

Sourcedocs.nexos.ai/changelog/changelog/latest-updatesread 2026-09-22

Work reaches agents through Portkey only when a client sends a request. Model, MCP and A2A calls are all made by the caller, and the Agent Gateway proxies them to the customer's agent servers. Portkey names no schedule, event, webhook or inbound queue that starts an agent run. The gateway waits for callers and does not wake an agent on its own.

Sourcedocs.portkey.ai/docs/product/agent-gatewayread 2026-09-22

Files added to a Project are chunked, embedded and stored in the Project's context index, and nexos.ai uses Retrieval-Augmented Generation to pull relevant context from them when answering. Projects can be shared with view or edit access. Agents take files from a Project as their knowledge base to give sourced answers, and that knowledge can be updated or removed at any time. New knowledge enters the persistent index without retraining and stays queryable beyond the context window.

Sourcedocs.nexos.ai/workspace/projectsread 2026-09-22

Embedding and file requests route through Portkey to providers, and responses are cached. Portkey maintains no retrieval structure over the customer's documents, and routing embedding calls builds none.

Sourceportkey.ai/pricingread 2026-09-22

User Memory keeps context about each user across chats and agents. The app adds context as the user works, and the user can view saved memories, edit them, delete one or all, or turn Memory off, alongside personalization details and custom instructions the user writes. Memory is scoped per user, in Chat and Agents, and users can delete their own entries, but nexos.ai states no lifetime for it.

Sourcedocs.nexos.ai/workspace/chat/memory-and-personalizationread 2026-09-22

Features cover routing, caching, observability, guardrails, prompt management and the MCP and agent gateways. None of them is a memory layer that keeps an agent's state or a user's context across sessions. The response cache holds model responses.

Sourceportkey.ai/pricingread 2026-09-22

Before any action that changes something in another tool, such as sending a message, creating a ticket or updating a record, Human-in-the-Loop Approvals pause the agent and show an approval card naming the action, the integration and its key details. The person approves (the agent acts and continues) or declines (the action is not taken and the run stops). Approvals appear in the conversation for chat agents and in Activity history for scheduled agents, and are switched on per integration inside each agent's settings.

Sourcedocs.nexos.ai/workspace/agents/human-in-the-loop-hitl-approvalsread 2026-09-22

Inputs and outputs pass through Portkey Guardrails, which act on the verdict automatically by denying the request, flagging it and letting it through, retrying or falling back. The MCP Gateway applies content filters per server, per user tool provisioning and rate limits on tool calls. Org and workspace admins can enforce guardrails, budgets and rate limits, so the customer sets these limits on what an agent may do. Portkey describes no step where a person reviews, approves or must validate an agent action before it commits.

Sourcedocs.portkey.ai/docs/product/guardrailsread 2026-09-22

Access is managed per user, as organization admins invite, update and remove users and assign each a role and team, and accounts can be managed through the customer's identity provider with linked SSO sign in. Company wide guardrails with per model overrides and exclusions apply across the workspace. nexos.ai states SOC 2 Type II and ISO 27001 certification, with reports in its Trust Center.

Sourcedocs.nexos.ai/workspace/settings/organization/usersread 2026-09-22

Enterprise plans get SSO through OIDC. Portkey also has fine grained role based access control, encrypted storage of provider keys, TLS 1.2+ in transit and AES-256 at rest. It claims compliance with SOC 2, ISO 27001, GDPR and HIPAA, with regular third party audits and penetration tests, and its Trust Center is at trust.portkey.ai. Enterprise includes SOC 2 Type 2 and custom BAAs. SCIM works with Okta and Microsoft Entra, and Portkey supports audit logs, JWT authentication and API key rotation.

Sourcedocs.portkey.ai/docs/product/enterprise-offering/security-portkeyread 2026-09-22

Every API request is recorded in Observability: which model was used, latency, cost, token usage and errors, with full request details, and admins can drill into a call to see the exact messages and responses, filtering by time, model, user or team. A Metrics dashboard shows usage, cost and health, and log spans are also recorded. Scheduled agents keep an Activity history of their runs and approvals, and retention is stated.

Sourcedocs.nexos.ai/workspace/settings/observabilityread 2026-09-22

Every tool call through the MCP Gateway is logged with the user, parameters and response, and the log can be filtered by server, user or time range. Model requests carry logs, traces, feedback, custom metadata, filters and alerts on every plan, with retention set per plan. Enterprise adds audit logs, logs export and OpenTelemetry export.

Sourcedocs.portkey.ai/docs/product/mcp-gatewayread 2026-09-22

The platform and most available models are hosted in Europe, and the EU gateway runs Claude, GPT, Gemini and Mistral EU hosted with zero data retention. nexos.ai gives no region list, customer environment option or way to choose a region.

Sourcenexos.ai/eu-gatewayread 2026-09-22

Enterprise offers private cloud deployment, VPC hosting and data isolation, and the open source gateway can be hosted by the customer. Hybrid deployments run on the customer's AWS (EKS, ECS, Marketplace), GCP and Azure (AKS, ACA), and air gapped deployment is available. A Gateway URLs setting points the dashboard at the customer's own self hosted AI and MCP gateways. Some of these options are Enterprise only.

Sourceportkey.ai/pricingread 2026-09-22

Users can start agents from premade templates, an extensive template library comes with every plan, and a prompt library of assistant instructions is organized by department, with entries such as a product strategy evaluator.

Sourcedocs.nexos.ai/workspace/agents/prompt-libraryread 2026-09-22

No ready made agents, workflows, templates or role specific agents ship with Portkey. The Prompt Library holds the customer's own templates, and the Skills Registry shares skills the team writes. The prebuilt assets are guardrail checks and partner guardrail integrations, which constrain what agents do.

Sourcedocs.portkey.ai/docs/product/guardrailsread 2026-09-22

Users pick any of 200+ models per chat, Project or agent, or let Smart Routing choose, and organization admins add models with their own guardrails, timeouts, ordered fallback models and a trusted-model badge. The Gateway API exposes the same catalog to the customer's code.

Sourcedocs.nexos.ai/workspace/settings/organization/modelsread 2026-09-22

Model choice sits with the customer. Portkey's Universal API puts many model providers behind one interface. Routing configs the customer writes set providers, model overrides, fallbacks, load balancing weights, retries, conditional routing and circuit breakers. Private model deployments on AWS, GCP and Azure are supported too.

Sourceportkey.ai/pricingread 2026-09-22

The Gateway API at api.nexos.ai has a published OpenAPI reference covering Chat, Anthropic native Messages, Responses, audio, images, embeddings and storage endpoints, plus management endpoints for teams, users, agents, assistants, company API keys, budget limits and usage, with Python, Go and .NET code examples. Agents can be managed from outside through it.

Sourcedocs.nexos.ai/gateway-apiread 2026-09-22

Developers get Portkey's own API and SDKs. The same feedback call works through the Node and Python SDKs and the REST API, and Portkey publishes an OpenAPI specification. Prompts are served through a Prompt API, and the Agent Gateway acts as a server to downstream agent clients for registered A2A agents.

Sourcedocs.portkey.ai/docs/product/observability/feedbackread 2026-09-22

Models can be compared side by side on the same prompt in nexos.ai Chat, the customer's own assistants can be added to Compare Models to test them against other models on performance and output differences, and Agent Builder has a Try Agent window for testing on real scenarios before launch. These let a person inspect and compare an agent's outputs by eye. There are no scored test cases, pass rate, judge verdict, quality gate or optimization loop.

Sourcedocs.nexos.ai/workspace/chatread 2026-09-22

Canary testing sends a set share of production traffic to a new model or prompt through a routing config, on every plan. Each request carries guardrail verdicts (pass or fail per check, counted in the log drawer) and weighted feedback scores sent through the Feedback API, which can be analyzed by metadata. Guardrails can deny, retry or fall back on a failed check. Together these let a team compare a change against current traffic.

Sourcedocs.portkey.ai/docs/product/ai-gateway/canary-testingread 2026-09-22

The Web Scraper fetches and analyzes web pages from URLs found in web search results, uploaded files and agent instructions, so agents continue tasks without a person supplying the link. The fetch is headless, and there is no hosted browser, desktop session or remote computer control that an agent drives.

Sourcedocs.nexos.ai/changelog/changelog/latest-updatesread 2026-09-22

The gateway routes model calls, including provider computer use tools, whose actions the customer's own code carries out. Portkey describes no browser, desktop or remote computer session that it runs for an agent, and it wires in no headless fetch or third party browser engine.

Sourceportkey.ai/pricingread 2026-09-22