Forem: Georgi Hristov

Help Me Pick a Name for My ASP.NET Debugging SaaS. https://dev.to/georgi_hristov/why-is-naming-a-developer-saas-harder-than-building-it-18no

Georgi Hristov — Wed, 06 May 2026 07:40:39 +0000

Georgi Hristov

May 6

Why is naming a developer SaaS harder than building it? 😅

#dotnet #webdev #saas #programming

Comments 3

1 min read

Why is naming a developer SaaS harder than building it? 😅

Georgi Hristov — Wed, 06 May 2026 07:30:31 +0000

I’m building a platform for replaying and debugging production API requests in ASP.NET apps and I’m stuck choosing the name.

Current options:

DebugSandbox
NetSandbox
TraceLive

Which one sounds best to you?

Or would you suggest something completely different?

Is it still worth building a SaaS in 2026… or is AI going to eat everything?

Georgi Hristov — Tue, 05 May 2026 17:50:44 +0000

Feels like every week there’s a new AI tool doing in minutes what used to take days.

So where does that leave us?

Are we still building real products…
or just wrapping APIs and calling it a SaaS?

I’m working on a small tool around debugging HTTP requests, and honestly I’m questioning this a bit.

Curious how others see it: Are you still building SaaS products right now? Or shifting more into AI-first tools?

What do you use to debug your ASP.NET Core APIs? I’m building a simpler tool for it. Would appreciate honest feedback.

Georgi Hristov — Tue, 05 May 2026 10:49:28 +0000

DebugProbe.AspNetCore: A Minimalist Tool for API Debugging

Georgi Hristov — Sun, 03 May 2026 09:01:10 +0000

My project is starting to get solid.

I really like how it’s starting to look. Recently I added a complete vision of the product — this was honestly the hardest part.

I’m trying to keep everything minimalistic. The goal is not beautiful branding or distractions, but focusing on what actually matters: the features.

As I mentioned, here are the features:

Capture HTTP requests & responses
Inspect headers, query, and body
JSON pretty formatting
Side-by-side response comparison
Built-in UI (/debug)
Zero configuration

The target is:

Debug real requests directly inside your app
No proxy setup or traffic interception
See exactly what your API sends and receives
Compare environments in seconds

Screenshots:

Requests

Request details

Compare

Compare across environments easily by entering:

Base URL
Trace ID

…and instantly see the differences.

In the next post, I’ll show how simple the setup is — it takes less than 2 minutes.

Debugging API is still painful

Georgi Hristov — Wed, 29 Apr 2026 08:53:57 +0000

Note: The image above is AI-generated to illustrate the idea.

Debugging APIs across environments is messy.

Logs are scattered
Responses differ between dev/staging
Errors like 401 appear with no clear reason

What I wanted
A simple way to:

See all requests in one place
Open a request and inspect it
Quickly understand failures

Also useful
Comparing the same request between environments.
You immediately see what’s different.

Built this as a small ASP.NET Core tool for myself.

Curious how others handle this problem.

Debugging HTTP Requests in ASP.NET Core Across Environments

Georgi Hristov — Wed, 29 Apr 2026 04:47:46 +0000

When the same HTTP request works in dev but fails in production, debugging gets messy fast.

Example: a request returns 200 in dev but 400 in prod because of a missing header or slightly different payload—and it’s not obvious why.

Most of the time, this means jumping between logs, Postman, and custom middleware, trying to spot the difference.

To simplify this, I started working on a lightweight way to capture and inspect HTTP requests and responses directly inside the app (headers, body, timing).

The idea is simple: capture everything in one place and compare requests across environments to quickly see what changed.

It’s still early stage, and I’m exploring better comparison and visualization.

How do you debug these cases today?

If you want to check it out:
GitHub: https://github.com/georgidhristov/DebugProbe.AspNetCore
NuGet: https://www.nuget.org/packages/DebugProbe.AspNetCore