For healthcare and financial-services engineering teams

Modernize the legacy .NET system nobody dares touch — and prove nothing broke.

Forgestus moves your .NET Framework application to modern .NET one piece at a time. Every piece is tested against how the system behaves today and goes live only when the results match — so the business keeps running, your auditors get a full record, and your code stays under your control.

Limited to 3 active pilots at a time Your own AI key · optional deployment in your own cloud account HIPAA/HITRUST controls built into the code the agents write
Sound familiar?

The system that runs your business is the one nobody wants to touch.

If you lead engineering at a healthcare organization, bank, credit union or insurer, you probably recognize at least one of these.

You’re one retirement away from a crisis.

The application behind your core operations runs on .NET Framework. The few people who really understand it are stretched thin, and hiring new engineers into a legacy stack is slow. What the system does lives in their heads.

WHAT CHANGES → Forgestus maps the whole system first and writes down what it does, so the knowledge lives in a report and a test suite instead of in two people’s memory.

OUTCOME A ranked, step-by-step plan before any code changes.

Every rewrite proposal dies on one question.

“How will we know the new system behaves the same?” A big-bang rewrite can’t answer it, so projects stall for years, get cancelled, or ship with surprises in production.

WHAT CHANGES → Forgestus records how your system behaves today, moves one slice at a time, and blocks any release where old and new results differ. You see the comparison for every slice.

OUTCOME Modernization you can show your CFO and your auditors: evidence, not assurances.

AI pilots die at security review.

Tools that send your code to a vendor’s cloud, with no record of what the AI touched, don’t survive the CISO and compliance. “An agent did it” is not an answer a regulator accepts.

WHAT CHANGES → You bring your own AI key, can run inside your own cloud account, and every AI action lands in a permanent audit ledger you can export.

OUTCOME AI-assisted work your security and compliance teams can review and approve.

What you get

From “trust us” to evidence on every change.

Modernization shouldn’t be a leap of faith. Here’s the difference.

 TodayWith Forgestus
KnowledgeNobody can say exactly what the system does.Business rules documented and pinned in tests that run on old and new.
RiskAn all-or-nothing rewrite with a cutover weekend.One slice at a time, with rollback ready at every step.
Evidence“Trust us, it works.”A before-and-after parity report per slice and a permanent audit ledger.
Platform.NET Framework on aging Windows servers.Modern .NET your team can keep supporting and hire for.
Your peopleBest engineers stuck keeping the legacy system alive.Senior engineers review and decide; agents do the repetitive port.
How it works

What working with us looks like.

Four steps, no big-bang commitment. You see evidence before you commit to anything larger.

See it

A free 30-minute demo. We walk through a sample migration end to end, including the parity report. No preparation needed.

Pilot, week 1: assess

A read-only assessment of your system ($7,500, credited toward your migration pilot or an annual plan). You get a system map, a ranked risk list, a step-by-step plan and a fixed quote. Nothing in your code changes.

Pilot: first slices, proven

We migrate the first slices. Each one ships with a before-and-after report showing the same tests giving the same results.

Roll out with evidence

Slice by slice, with a gradual cutover and rollback ready. Your auditors get the parity reports and the audit ledger.

A worked example

What week 1 looks like for a claims system

This is a sample from our assessment report, built on an illustrative codebase — not a customer. The system is a WebForms and WCF claims platform on .NET Framework 4.8: 42 pages, an Entity Framework data layer, a 118-table SQL Server project, and 12% test coverage.

Read the full sample assessment (PDF) →

WHAT THE ASSESSMENT TOLD THE TEAM
  • Where the risk is. The claims page ranked critical, the billing service high. Everything else is lower.
  • Where to start. Lowest-risk module first to prove the approach, then the service layer, with the web UI last behind a facade.
  • What needs a human. One service uses a connection type that doesn’t port automatically; two SQL CLR assemblies need a DBA review. Flagged, not guessed.
  • What happens next. A proposed pilot for the first three slices, with a fixed quote.
Proof

See the evidence before you spend a dollar.

We’re early, and we won’t dress that up. What we can do is show you exactly what you would receive.

Sample assessment

What you get in week 1

A system map, risk register, dependency-ordered plan and proposed pilot, generated on an illustrative codebase.

Open the sample (PDF) →
Parity report

What you get for every slice

A before-and-after report: the same tests, run on the old system and the new one, with every difference listed. We’ll walk you through one in the demo.

Book a demo →
Design-partner pilots

Three spots, shared openly

We take on no more than three active pilots at a time so each one gets founder-level attention, and we’re happy to share what we learn with you along the way.

Book a demo →
Who’s behind it

Built by someone who has run these systems.

I’m Victor Gorbachev. I spent 20 years building enterprise .NET systems — writing the code myself early on, then leading product for platforms running at real scale. Most recently I led product for a banking and insurance platform at Deloitte; before that I spent 11 years at Access Softek building digital banking software for credit unions and banks, and earlier built software for healthcare records audits.

I’ve watched the same story play out for two decades: a legacy .NET system nobody wants to touch, a rewrite that quietly becomes a multi-year project, and the “broken” system still running the business underneath. AI agents are finally good enough to help — but only if you can prove they didn’t quietly change what the system does. That’s what Forgestus is built to prove.

Why not just use Copilot or AWS Transform?

Upgrade assistants help developers. We prove the result.

GitHub Copilot app modernization and AWS Transform are good tools, and for a small, well-tested application an assistant may be all you need. For a system you can’t afford to get wrong, the difference is in how correctness is shown.

 Upgrade assistantsForgestus
How the work gets doneA developer drives the tool, project by project, and reviews the changes.Agents do the port slice by slice, from a whole-system plan. Your engineers review.
How correctness is checkedFocus on getting the code to build and run. Confirming behavior is left to your team.Tests pinned on the old system must give the same results on the new one before a slice can merge.
What your auditors receiveChange history and the tool’s own build and transformation reports.A parity report per slice and a permanent audit ledger of every AI call and its cost.
Where your code goesYour code is processed by the vendor’s AI service.Your own AI key on every plan; on Enterprise, deployment inside your own AWS account.
Planning the whole estatePer-project upgrade plans.A ranked, dependency-ordered plan for the whole system, with gradual cutover and rollback.

Based on the vendors’ public documentation as of November 2026 (AWS Transform, GitHub Copilot app modernization). These tools change quickly; check each vendor for current capabilities.

Security & compliance

Built so your security team can say yes.

Regulated teams don’t need another black box. Here is what we do, and what we don’t claim yet.

Your keys, your AI vendor

Forgestus runs on your own Anthropic, AWS Bedrock, OpenAI or Google Vertex credentials. Your vendor bills you directly, under your contract and your data-handling terms.

Your cloud account (Enterprise)

Enterprise customers can run Forgestus in their own AWS account, so orchestration, storage and compute stay inside their data boundary.

A permanent audit ledger

Every AI call, every retry and every dollar is recorded and never expires. Export it to CSV for your auditors. SIEM connectors are on our roadmap.

HIPAA and HITRUST coding controls

Rules for PHI in logs, encryption, audit trails and least-privilege access are applied to the code the agents write, and reviewer agents flag violations. These controls support your compliance program; they don’t replace it.

Humans stay in control

When something doesn’t port cleanly, agents flag it for a person instead of guessing. When an agent can’t proceed, it stops and asks.

Where we are today

SOC 2 and FedRAMP are on our roadmap; we are not certified yet. We’ll complete your security questionnaire during the pilot, and our guardrails ↗ are public.

Pricing

Start small. Pay for proof before you pay for scale.

A demo is free. A pilot starts with a one-week, read-only assessment at $7,500, credited in full toward your migration pilot or an annual plan. After that, a flat platform fee with infrastructure included — you pay your own AI vendor only for model usage.

Team

$1,000/month
For a small product team.
  • Up to 3 connected repos
  • Core stacks: Node, React, Flutter
  • Your own AI key (Anthropic)
Book a demo

Enterprise

Let’s talk
For regulated and large organizations.
  • Deployment in your own AWS account
  • Unlimited repos; multi-vendor AI keys
  • Direct-with-founder support
Book a demo

Compare every plan feature, side by side →  ·  How the platform works →

Annual billing is 15% off. The assessment credit applies to a migration pilot or an annual plan signed within 90 days of your readout.

FAQ

Questions leaders and engineers ask.

For leadership and procurement

How do we get started, and what does it cost?
Book a free 30-minute demo. If it’s a fit, a pilot begins with a one-week, read-only assessment ($7,500) that produces a system map, a ranked risk list, a step-by-step plan and a fixed quote for the first migration slices. The fee is credited in full toward the migration pilot or an annual plan signed within 90 days of your readout. Nothing in your code changes during the assessment.
How is this different from a rewrite, or from an upgrade assistant?
A rewrite replaces the system all at once and can’t show it behaves the same. An upgrade assistant helps a developer port code, and leaves behavior testing to your team. Forgestus moves one slice at a time and blocks release unless tests pinned on your current system give the same results on the new one. See the comparison above.
Does our code leave our environment?
On every plan you bring your own AI key, so model usage is under your contract and data-handling terms. Team and Business run in our managed cloud. Enterprise customers can deploy Forgestus in their own AWS account so orchestration, storage and compute stay inside their boundary.
What about HIPAA, HITRUST, SOC 2 and FedRAMP?
HIPAA and HITRUST coding controls (PHI logging rules, encryption, audit trails, least-privilege access) are applied to the code Forgestus writes for you, and reviewer agents flag violations. They support your compliance program but don’t replace it. SOC 2 and FedRAMP are on our roadmap and we are not certified yet. PCI-DSS is available through custom onboarding.
What if an agent gets stuck or something doesn’t port cleanly?
Agents don’t guess. Anything non-portable is flagged for a human, and an agent that can’t find what it needs stops and asks instead of burning budget. Every blocker is shown with a plain diagnosis and the exact next step.
Who is behind Forgestus, and how many customers can you take?
Forgestus was founded by Victor Gorbachev, a 20-year enterprise .NET engineer and product leader. We take no more than three active pilots at a time so each gets founder-level attention.

For engineering teams

What stacks do you actually support?
Node, modern .NET 10, classic .NET Framework 4.x on a Windows Fargate runner, React, React + Vite, Next.js, Angular, Blazor, Flutter, Unity, C# Windows desktop (WPF / WinForms), C# Windows Services, and SSDT. The full .NET family — including classic .NET Framework on Windows runners — is available on the Business plan; Unity and custom stack onboarding (Rust, Go, Elixir, Kotlin/Android-native) are Enterprise. See the platform →
How do the HIPAA / HITRUST controls work?
Add compliance: [hipaa, hitrust] to forge.yaml and every agent inherits the coding constraints — PHI logging rules, KMS encryption, audit-trail patterns, least-privilege IAM, DLQ requirements. Enforced by the runtime, hard-flagged by the reviewer agents.
What counts as an epic, and what happens at my monthly limit?
An epic is one GitHub issue you file and /proceed — however many stories the planner breaks it into. Team includes 20 epics/month, Business 75; beyond that, additional epics are billed per-epic ($40 Team, $30 Business) — nothing stops mid-flight, and in-progress epics always run to completion. Epics on Windows runners (classic .NET Framework, WPF/WinForms, SSDT) count as two, reflecting the heavier compute. Enterprise plans are unlimited because they run in your own AWS account.
Do I really bring my own AI vendor key?
Yes, on every tier. Forgestus runs against your Anthropic key, AWS Bedrock credentials (Business+), OpenAI key (Enterprise), or Google Vertex credentials (Enterprise). Your AI vendor invoices you directly at your contract rate — model tokens are the only usage cost you pay. On Team and Business we run everything in our managed cloud and the flat platform fee covers all infrastructure (Fargate runners, orchestration, storage) — you never see an AWS bill. Only Enterprise customers who self-host in their own AWS account pay AWS directly, and they can opt into Forgestus-managed compute with a 10–15% pass-through for a single invoice.
Can I customize the agent pipeline?
On Enterprise, yes. You can prepend project-specific constraints to any built-in agent’s prompt — or override it entirely — without losing the battle-tested defaults, and Forgestus auto-refreshes a per-repo learnings skill weekly, so the agents get smarter about your codebase over time. Fully custom agent types injected at specific pipeline stages (e.g. a security pass after backend) are in early access — ask us about it.
What is the advisor tool?
A way to get frontier-model judgment at fast-model cost. A quick executor agent runs the bulk of the work, but when it hits a genuinely hard decision it consults a higher-intelligence advisor model mid-task (Claude Opus by default — or whichever model you route it to) — and keeps going with the answer. You pay the advisor rate only for the moments that need it, not for the whole run. Enable it per-project and per-agent in forge.yaml; advisor token usage and cost are itemized separately on every audit row. Available on Enterprise, on your own provider keys.
Is this self-hosted? Can I run it in my own VPC?
Enterprise customers can deploy Forgestus in their own AWS account as a VPC deployment — the orchestrator Lambda, DynamoDB, ECS Fargate, and S3 storage all run in your account, with Forgestus providing the agent images and release cadence. Team and Business tiers run in our managed cloud.
Free · 30 minutes

Know exactly what modernizing your legacy system will take.

Book a demo and we’ll walk through a sample migration end to end, then look at your system together. If it’s a fit, a pilot starts with a one-week, read-only assessment ($7,500, credited in full toward your migration pilot or an annual plan).

Prefer email? contact@forgestus.ai

“You can outsource your thinking — but you can’t outsource your understanding.” Forgestus automates the work. Your team keeps the judgment.