Model freedom
Claude, GPT, Gemini and 400+ other models through their providers’ APIs, Auto Mode on models hosted in India, your own keys and endpoints, or open-weight models on your own GPUs. Switch without switching tools.
Claude, GPT, Gemini and 400+ other models through their providers’ APIs, Auto Mode on models hosted in India, your own keys and endpoints, or open-weight models on your own GPUs. Switch without switching tools.
The same product in Sypha Cloud, in your private cloud, or fully on premises and air-gapped. The capability never depends on where it runs.
Agent settings for the organisation, a team, a role or one member, each level only stricter than the one above. Budgets, safety alerts and audit beside them, enforced in every IDE and the CLI.
Agents your team writes once, a rule for every tool, a sandbox for commands, memory that carries over, a record of every run and a browser of its own.
Write a specialist once, such as a code reviewer, a test writer or a security auditor, and give it to everyone or to chosen teams. Members call it with @ in the editor and the CLI.
For each tool, choose Allow, Ask or Deny. Add exceptions for paths and commands: let git run freely, never read .env files, block destructive deletes.
Run the agent’s shell commands inside an operating-system sandbox. They can write only inside the project and reach only the network addresses you allow.
The agent saves lasting facts about your project as it works, and compacts long sessions before they run out of room, so each new task starts with what the last one learned.
Follow a prompt through every subagent it started. If a run fails, see where it failed, why, and what to do next, in plain language.
Web search works with models from every provider, and the agent can open a browser to click through a page and take screenshots, under the same permissions.
From understanding a codebase to shipping in parallel.
A codebase is more than the file in front of you. CodeGraph connects symbols, callers and dependencies so you can explore the impact of a change.
Plan the change, work across files, run the terminal and debug what comes back. Use a focused agent, or let Orchestrator split the work and hand it to subagents.
An empty cart costs nothing.
Add a test to prove it.
The Agent Manager gives every task its own worktree, a separate folder and branch, so agents work side by side without touching the same files. When a check fails or a reviewer comments, send it back: the agent commits and pushes the fix.
Context, tools, models and safeguards that make an agentic engineer useful on the second day, and the hundredth.
Reference files, folders, problems, terminal output and git changes with @ mentions. Project rules and AGENTS.md carry your conventions into every session.
A live map of every symbol, caller, import chain and test. See the impact radius of a change before it merges, and hand the graph to Plan.
Package repeatable work as slash commands: /review, /test-gen, /doc-gen and /security-audit ship with the product, and teams share a vetted library.
Native MCP connects issue trackers, internal APIs and databases. Terminal and browser actions run within the permissions your organisation sets.
Let Auto Mode pick from models hosted in India, or choose Claude, GPT, Gemini and 400+ more through their providers’ APIs, your own keys or local models. Organisation settings decide who sees what.
VS Code, the JetBrains family and the CLI share one login, the same agents and the same settings. Changes your organisation saves reach all three on their own.
Model and tool availability depends on your plan, provider and organisation policy.
The capability never depends on where it runs. Start in Sypha Cloud, move to your cloud or your own data centre later, and keep the same product, controls and workflows.
A managed service with two routes to inference: open-weight models hosted in India, where Auto Mode can pick the model for each request, or 400+ models such as Claude, GPT and Gemini called through their providers’ own APIs via the Sypha gateway. We do not host those; we route to them. Nothing to run.
Deploy on Vertex AI, Bedrock, Azure or OCI under your own contracts, self-host open models on cloud GPUs, or run the application layer in a sovereign Indian data centre.
The full stack on your own GPUs behind your own perimeter, with air-gapped options. Self-hosted open-source models only, no outbound calls, and the audit trail on your storage.
Hybrid, under one console: regulated production on premises, experimentation in Sypha Cloud, the same controls throughout.
Enterprise deploymentGive developers room to work. Decide what their agents may do, give every team its specialists and its budget, and follow every run, in one dashboard.
Explore SyphaCode for teamsReadRead filesAllowAskDenyEditCreate or change filesAllowAskDenyBashOrganisation set AskAllowAskDenyBashAskDenyReviews every change for bugs, style and missing tests.
Published to 2 teamsCompleted · 3 tasks · 1 issue recovered
Stopped by a safety check
Last 7 days1 file write stopped1 prompt and 1 file write stopped
Analytics covers traffic routed through Sypha Gateway. Direct BYOK requests are outside that reporting path.
SyphaCode is SYPHA’s agentic coding tool: AI agents across a VS Code extension, the JetBrains family and a terminal CLI, on one account with one set of models and policies. They understand existing code, plan and build changes, run tests and review the result, several tasks at once if you like, and you approve what lands.
Five you can pick: Orchestrator coordinates work across agents, Plan plans the change before anything is edited, Code writes and edits code, Debug diagnoses and fixes issues, and Ask answers questions without changing code. Two more, Explore and General, take the searches and side tasks the others hand off. In the editor they appear as modes in the picker, and each can have its own model.
Yes. The Agent Manager gives each task its own Git worktree, a separate folder and branch, so agents work side by side without editing the same files and your own checkout stays as it is. Pull request status shows beside each branch, and a failing check or a review comment can go straight back to the agent, which commits and pushes the fix.
Yes. Organisation admins publish team agents, such as a code reviewer, a test writer or a security auditor, to everyone or to chosen teams, each with its own instructions, tool access and model. Members call them with @ next to the built-in agents, and an enforced agent cannot be replaced. Members can also create their own, import agent files or take them from the marketplace.
In Sypha Cloud, two kinds: open-weight models we host in India, which Auto Mode can choose between for each request, and more than 400 models such as Claude, GPT and Gemini, which we do not host but call through their providers’ own APIs via the Sypha gateway. On any plan you can also bring your own provider keys or connect local models through Ollama, LM Studio or an OpenAI-compatible endpoint, and an organisation can add its own endpoints for every member. Organisation settings decide which ones appear.
Each tool, from reading and editing files to shell commands, web access and MCP, is set to Allow, Ask or Deny, with exceptions for particular paths and commands, such as letting git run freely or never reading .env files. With the sandbox on, commands can write only inside the project and reach only the network destinations you allow.
Yes. Private cloud deployments run on Vertex AI, Bedrock, Azure or OCI under your contracts, or in a sovereign Indian data centre. On-premises deployments run the full stack on your GPUs, with an air-gapped option using self-hosted open-source models.
The Free plan is free forever with your own keys and needs no credit card. Paid plans add the Sypha gateway, Auto Mode, the CLI and team features.