Reuse eligible plan access
Authenticate with supported provider CLIs and keep the account relationship you already have.
Included route
AI coding agents for C# and .NET
Use any AI coding agent.
Inside Visual Studio 2026.
Connect Databricks Unity Catalog, Codex, Kiro, Gemini, Kimi, DeepSeek, OpenRouter, or local Ollama models to your C# and .NET solutions. Keep the IDE and provider access you already use.
No mandatory second pay-as-you-go API bill.
AI providers for C# and .NET in Visual Studio 2026
Explore every provider →
Featured enterprise integration
Databricks Unity Catalog
Bring the chat-capable Model Serving endpoints approved in your Databricks workspace into Visual Studio 2026. iolys discovers the available endpoints while your organization keeps model access, governance, and usage in Databricks.
Model Serving discovery
Multiple model families
Enterprise-controlled access
Explore Databricks Unity Catalog →
Built for Visual Studio
Find iolys where Visual Studio developers already look.
The Marketplace preview makes the product tangible early: iolys is a native Visual Studio 2026 extension, ready to install where your C# and .NET work already happens.
View on the MarketplaceBrowseInstalledUpdates
Search (Ctrl+L)
iolys
Install
Navigate AI providers and coding agents from one Visual Studio workspace…
iolys
iolysAI agents for Visual Studio 2026
Your compass through AI
Connect the right coding agent to your C# and .NET solution without leaving Visual Studio.
A major iolys advantage
Use the subscriptions you already pay for.
With supported provider CLIs, eligible Codex, Gemini, Kimi, and Kiro account access can travel into Visual Studio 2026. You are not forced to create a second, metered API setup just to use AI while developing C# and .NET applications.
See pricing
Databricks, local models, and APIs
Connect Databricks Unity Catalog, use Ollama locally, or bring your own API credentials whenever that route fits better.
Your infrastructure. Your billing.The problem
.NET developers should not be locked into one AI coding assistant.
AI models improve quickly, but switching providers still pushes C# developers toward another editor, another interface, and another workflow outside Visual Studio 2026.
Provider lock-in
Your .NET development workflow becomes tied to one vendor’s roadmap, models, and pricing.
Constant context switching
Powerful agents live outside Visual Studio 2026, separating the work from the code.
Local models left behind
Private and self-hosted options rarely fit naturally into the Visual Studio 2026 workflow.
The provider layer
One Visual Studio 2026 workspace.
Every useful route to AI.
iolys connects your C# and .NET solutions to multiple AI coding agents, so the provider can change while your development workflow stays familiar.
Switch providers, not workflows
Move between providers and models without relearning your tools or leaving the active C# solution.
Use provider CLIs
Bring capable AI coding agents such as Codex, Gemini, Kimi, and Kiro into Visual Studio 2026 for C# and .NET work.
Connect APIs your way
Use OpenAI-compatible endpoints and Databricks Unity Catalog workspaces across cloud services and self-hosted infrastructure.
Run local with Ollama
Keep sensitive work close and use the local models that fit your machine and priorities.
Stay oriented
See the active machine, solution, workspace, session, provider, and model before work begins.
Keep control
Review tool activity, affected files, permissions, and sensitive actions in plain language.
Freedom by design
Use the AI access you already have for .NET development.
Your provider strategy should match the task—not the limitations of an extension.
Choose a subscription-backed CLI for agentic work, an API when you need direct model access, or a local endpoint when privacy and control matter most.
Existing subscriptions
Connect supported provider CLIs and keep the plans you already pay for.
Cloud and self-hosted
Point iolys at OpenAI-compatible services or a Databricks Unity Catalog workspace and choose the right endpoint.
Models on your machine
Work through Ollama without sending every task to a cloud provider.
How it works
Change the intelligence.
Keep the course.
-
01
Connect
Add a provider CLI, API endpoint, or local Ollama instance.
-
02
Choose
Select the provider and model that best fit the current task.
-
03
Work
Stay inside Visual Studio 2026 with one conversation and a clear view of activity.
Why iolys exists
C# and .NET developers deserve the same freedom to choose.
Most AI coding innovation has centered on VS Code, while developers building C# and .NET applications in Visual Studio 2026 remain tied to a much narrower set of choices. iolys was built to change that.
Instead of asking developers to change tools whenever a better model appears, iolys lets the AI change behind a consistent, trustworthy Visual Studio 2026 experience.
Simple annual pricing
Choose the plan that fits your team.
iolys pricing covers the Visual Studio 2026 extension for your C# and .NET projects. Your provider subscriptions, API accounts, and local infrastructure stay yours.
Community
Free
For eligible open-source projects
- Visual Studio 2026 extension for C# and .NET
- Supported provider connections
- Community support on Discord
Recommended
Pro
$75 / year
For one individual user
- Everything in Community
- Commercial C# and .NET project use
- One named user
Enterprise
$100 / user / year
For volume purchasing and organizations
- Volume licensing for .NET teams
- SSO support
- More administrative control
FAQ
Clear answers before you choose a route.
Does iolys support C# and .NET projects?
Yes. iolys works from the active Visual Studio 2026 solution, including C# projects, .NET applications, libraries, tests, and multi-project solutions.
Is iolys an AI provider?
No. iolys is a provider-independent workspace that connects Visual Studio 2026 to models, agents, CLIs, and compatible APIs.
Can I use my existing AI subscriptions?
Yes. Where a supported provider CLI uses eligible account-based access, iolys brings that route into Visual Studio 2026. You do not have to buy separate pay-as-you-go API access for those connections.
Does it support local models?
Yes. iolys supports Ollama and is designed to work with local and self-hosted model routes alongside cloud providers.
Do I need to leave Visual Studio 2026?
No. The extension is built specifically for Visual Studio 2026 so conversations, workspace context, and agent activity stay close to your code.
What happens when I change providers?
The provider and model change; the core iolys interface, navigation, permission flow, and workspace context remain consistent.
Choose your next model, not your next workflow
Bring the right AI coding agent to your .NET solution.
One Visual Studio 2026 extension for C#, .NET, and the changing world of AI providers.
Get iolys for Visual Studio 2026