// .NET CONSULTING

We help .NET teams build the world's most important software

Distributed systems, performance, resiliency, and agent systems, from the team that created Akka.NET. Your stack doesn't need to include Akka.NET.

Talk with Aaron See our work

Free 20-minute call with Aaron Stannard, creator of Akka.NET. No prep needed.

100+ customers
Since 2015 building mission-critical .NET systems
1 business day response time
ref: problems

// PROBLEMS

Sound familiar?

It works in staging and breaks in production.

Real load, restarts, and network failures expose bugs your tests never found.

A long job runs and nobody knows if it's alive.

A Task is pending or done. It can't tell you whether the work is still moving.

Adding hardware stopped helping.

Throughput hit a wall, and you can't say which limit you reached.

A bug appears once a week and vanishes under a debugger.

Races, duplicate work, and lost messages are hard to see and harder to reproduce.

Nobody has checked the design.

Traffic, data, or the team is about to grow, and you want a second opinion first.

ref: results

// RESULTS

Hard problems, fixed

Consulting

A utility IoT network was losing 70-80% of its connections

About 1 million meters connected at once, and 70-80% of those connections failed, so meter data never got saved. We built a lab that reproduced production load: k6 tests across 200 pods on a 5-machine Kubernetes cluster, with OpenTelemetry metrics and Grafana dashboards. The bottlenecks sat in the network stack and the Linux kernel TCP settings. We shipped Akka.IO improvements, kernel tuning, and better load distribution.

Read the full story →

Support customer since 2023

Priva: a 70-hour bug with roots in 2015

Priva makes climate control for greenhouses and buildings, with thousands of IoT gateways in the field. A cluster singleton hand-off bug, rooted in code from 2015, was hitting them. Tracking it down took more than 70 hours. We fixed it in Akka.NET v1.5.27, so every Akka.NET user got the fix. A former Petabridge engineer also built tools Priva runs in production, such as Akka.Discovery.Azure.

It works really well, I need to say that. Wessel, tech lead at Priva
Read the full story →

Training and build

SNL Financial: from 7,000 to 840,000 grids

Joel Mueller, a software architect at SNL Financial, built a multi-user forecasting module on Akka.NET and took our training mid-project. When his biggest client asked to go from 7,000 grids to 840,000, the product held up and shipped on time.

Performance in the product I described was so great with 7,000 (!) excel-style grids, our biggest client decided to bump it up to 840,000 (!!) grids, a 120x increase. Yesterday. That got a little bit hectic… We shipped on time, though! Joel Mueller, Software Architect, SNL Financial
Read the full story →

Have a problem like these?

Tell Aaron on a 20-minute call. If we can't help, we'll say so.

Talk with Aaron
ref: services

// SERVICES

Four ways we help

Every engagement is fixed price and ends with a written report.

Architecture review

We read your design, talk to your team, and test the risky parts. You get a written report that names what will break first and how to fix it.

Code review

Our engineers read your source for bugs, performance problems, and design flaws. Each finding comes with a specific fix.

Implementation

We build the hard parts with your team: services, plugins, performance tests, and CI/CD.

New

Streaming and background work review

Long-running jobs, streams, and background work fail in ways request/response code doesn't: jobs that die quietly, consumers that fall behind, work lost on restart. We review how your .NET system handles them, whether you use IAsyncEnumerable, Channels, Kafka, actors, or AI agents that run for minutes. We don't care which framework you use.

What we check

  • How you tell a slow job from a dead one
  • What happens when a producer outruns its consumer
  • How work recovers after a crash or restart
  • How progress and results reach the people waiting on them

Fixed price, quoted after a short call.

Talk with Aaron

Covered in our Oct 30 webinar →

ref: process

// PROCESS

How an engagement works

01

Call

20 minutes, no prep. Tell us what you're building and where you need help. We tell you straight whether we can help.

02

Scope

We send a fixed-price proposal with deliverables and a timeline. No open-ended billing.

03

Deliver

We check in as we go. When a problem only shows up under load, we reproduce it in our lab.

04

Report

You get written recommendations specific to your code. Every engagement ends with one.

Sample Petabridge architecture review document

A sample architecture review. Every engagement ends with a written report like this.

ref: proof

// CLIENTS

Who we work with

Our clients include Bank of America, Boeing, Apple, Dell, and 100+ other teams running .NET in production.

Bank of America JPMorgan Chase Boeing Airbus Apple Dell McKesson Schneider Electric United Airlines BMW

Teams in finance, insurance, healthcare, energy, transportation, and aerospace & defense. See all customers →

In pre-production development, we applied Petabridge's expertise to review our design decisions and approach, which taught me more about the framework, saved us a few production issues, and most importantly really gave us the confidence to proceed.

When combined with the training programs that Petabridge offers, it's been a no-brainer for our team and a great return on our investment to date.

Sean Killeen VP, Innovation & Products, SCT Software

With Petabridge, you get direct access to the people who actually write the framework. … You're not dealing with tier three support.

Jason Shave Engineering Manager, Luware Read the Luware case study →
ref: faq

// FAQ

Questions we get

Do we need to use Akka.NET?

No. We review and fix distributed .NET systems whether or not they use Akka.NET. Akka.NET is why we know this problem space. It's not a requirement to work with us.

What does it cost?

Every engagement is fixed price. After a short call we quote the work, and you know the cost before we start. We don't bill open-ended hours.

Can you sign an NDA?

Yes. Send yours before the call or after it. We work with teams that can't share code or architecture details without one.

What happens on the 20-minute call?

You tell us what you're building and where you need help. We ask questions and say whether we can help. If we can, we send a fixed-price proposal. There's nothing to prepare, and no obligation.

ref: contact

// CONTACT

Tell us what you're building

The fastest way to start is a 20-minute call. No prep, no commitment. Prefer to write? Use the form or email us.

Talk with Aaron

Or send the details

Or email [email protected]

Fixed-price quotes. No open-ended billing.

We reply within one business day.

ref: newsletter

// STAY_CONNECTED