We just shipped a new guide for using Portkey with Conductor, the macOS AI coding app built on top of Claude Code.

With Portkey, you can:

• plug into 1600+ models through Portkey’s gateway,

• add fallbacks, load balancing, caching and routing,

• set cost / token limits for long agentic coding sessions,
• get full request‑level logs and metrics for every session.

To implement Portkey with conductor, checkout the docs here

You can now point Portkey at credentials in AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault instead of pasting keys in the product—using secret_mappings so values are fetched at runtime.

This means:

→ Sensitive material stays in vaults you already control and audit

→ Integrations and virtual keys reference secrets by mapping, not plaintext

→ Rotation and access policies live where your infra team expects them

Set it up for your org ->

Sometimes your guardrails have dependencies. You might want to:

→ Run a PII detection check first, then only run compliance validation on the sanitized output

→ Check the request format before running an expensive LLM-based content safety check

→ Validate HIPAA compliance before running clinical content checks — no point evaluating medical accuracy if the request already violates patient data regulations

With the new sequential flag, checks run one after another in the order you define, and if an earlier check fails, the rest don't execute.

See how you can set up sequential guardrails →

We have some exciting news to share: Portkey has officially closed our $15M Series A !!

Huge thanks to our investors at Elevation and Lightspeed, as well as our team and community for getting us here.

You have pushed us to be better, given us helpful feedback, and suggested the features that have made Portkey what it is today!

This funding will continue expanding our go-to-market presence, deepen our governance capabilities for agentic AI, and scale the gateway that enterprises rely on to run AI in production.

What’s more, we’re making our core enterprise gateway available for free so that all teams have access to governance and observability when they need it!!

You can now route requests with the same identifier consistently to the same target when load balancing.

This means:

→ Conversation context stays intact across multiple requests

→ A/B tests produce consistent, reliable results

→ Users get session-based routing for personalized experiences

See how to set up this config ->

Claude Sonnet 4.6 is Anthropic's new default model, delivering near-Opus level reasoning and a 1M token context window, all at mid-tier pricing. Built for agentic workflows, computer use, and long-context tasks.

With Portkey, bring Claude Sonnet 4.6 into production with:

✅ Unified access via the AI Gateway

✅ Consistent guardrails and policy enforcement

✅ Full observability across logs, latency, and spend

✅ Team-level budgets and rate-limits

GPT-5.3-Codex is OpenAI’s latest model, designed for agentic, long-running coding workflows, covering everything from multi-step refactors to debugging across large repositories.

With Portkey, you can bring GPT-5.3-Codex into production with:

✅ Unified access via the AI Gateway

✅ Consistent guardrails and policy enforcement

✅ Full observability across logs, latency, and spend

✅ Team-level budgets and rate-limit controls

After this date, the model will no longer be available or operable. This also impacts fine-tuned models built on top of this base model.

If you’re using Mistral-large-2411 in production, it’s a good time to review deployments and plan a migration to supported alternatives.

Google is deprecating Gemini 2.0 Flash and Gemini 2.0 Flash Lite on March 31, 2026 across Gemini API and Google AI Studio.

If your apps or agents rely on these models, you’ll need to migrate to supported alternatives like Gemini 2.5 Flash or 2.5 Flash Lite before that date.

MCP adoption is accelerating rapidly, with servers and tools now being used across teams, environments, and agent workflows.

As MCP usage scales, teams start running into a consistent set of challenges:

• authentication varies across MCP servers
• access to tools becomes difficult to govern
• visibility into MCP usage is limited

Portkey’s MCP Gateway solves this!

It is a control layer to securely connect MCP servers, standardize authentication, manage tool access, and get clear visibility into MCP usage, without changing existing agents or MCP servers.

Check it out ->