Build, deploy, and host ASP.NET Core apps with BlackSails—without turning cloud infrastructure into your full-time job.
~/acme/Billing.Api
$ blacksails deploy
billing-api
ASP.NET Core · BlackSails
Production URL
billing-acme.apps.blacksails.sh
A native path from your .NET project to production
One opinionated platform
Keep writing .NET. BlackSails handles the repeatable deployment work, runtime, service isolation, and delivery.
Build
Start with an ASP.NET Core project. BlackSails validates the .csproj and publishes locally with the CLI or on an isolated, OIDC-attested Runnable runner.
src/Billing.Api/
├─Billing.Api.csproj
├─Program.cs
└─appsettings.json
Isolate
Workspace, application, and environment coordinates make services explicit, isolated, and safe to update.
Deliver
Deploy through BlackSails, reuse the same service on every release, and receive a production HTTPS endpoint automatically.
Production
billing-acme.apps.blacksails.sh
HTTPS ready
The deployment workflow
BlackSails reduces the release loop to a repeatable build—on your machine or Runnable—and an immutable deployment your team can inspect.
Run blacksails init inside a standard ASP.NET Core project. BlackSails links it to a stable application and production URL.
Publish locally with the CLI or start an isolated Runnable build from BlackSails. Both paths create the same verified immutable artifact.
BlackSails starts the release, waits for health checks, preserves the previous version on failure, and returns your HTTPS endpoint.
See what ships
This example ASP.NET Core service was packaged and deployed through BlackSails. Open it and verify the result yourself.
Open the live serviceBlackSails / demos / hello-web
Hello from .NET
Deployed with BlackSails
Bring your ASP.NET Core project. BlackSails handles everything between your code and a live service.
$ blacksails deploy
