01
Depth beats breadth
One excellent path for ASP.NET Core is more useful than a hundred half-supported deployment targets. BlackSails is intentionally specific about what it runs.
About BlackSails
A developer cloud with a point of view.
BlackSails is built around a simple belief: shipping an ASP.NET Core service should feel like the natural last step of building one.
The problem
The app is ready. The infrastructure project is just beginning.
.NET teams know how to build reliable web applications. Too often, putting one online means learning container registries, image pipelines, health probes, ingress, certificates, secret stores, and provider-specific billing before the first request ever arrives.
BlackSails turns that infrastructure project into a platform contract: give us a supported web project, build it locally or with Runnable, and get back an isolated, healthy service on a stable HTTPS URL.
The goal is not to make infrastructure mysterious. It is to make infrastructure stop interrupting the product.
Our mission
Make production feel native to the .NET development loop.
1
command to build and release
3
supported .NET generations
0
Dockerfiles required
How we build
Four principles for the voyage.
02
Local work should stay valuable
If a project already builds on a developer's machine, production should not require rebuilding that context inside a proprietary remote pipeline.
03
The safe path should be the short path
Immutable releases, health-gated promotion, bounded retries, isolation, and spending limits belong in the default workflow—not in an advanced setup guide.
04
Abstractions should stay honest
BlackSails hides provider machinery from the product surface, but keeps the things developers need to reason about visible: artifacts, releases, logs, health, and cost.
Built for the part after dotnet run.
Bring a supported ASP.NET Core project and turn the build you trust into a production release.