Skip to content

The BlackSails platform

Everything a .NET service needs to reach production.

A deliberately focused cloud for ASP.NET Core—from a local or Runnable dotnet publish to a healthy HTTPS service, with fewer moving parts in between.

01From source to artifact

A deployment path that understands .NET.

BlackSails starts with the project format and commands your team already knows. Build locally with the CLI or on an isolated Runnable runner; both paths upload only the finished release.

  • ASP.NET Core projects targeting .NET 8, 9, or 10
  • Release-mode, framework-dependent Linux x64 publish
  • Deterministic archives verified with SHA-256
  • Resumable uploads for large artifacts
  • Runnable OIDC attestation with no Dockerfile to maintain
  • GitHub Actions deployments with expiring, scoped service tokens
~/acme/Billing.Api

$ blacksails deploy

ProjectBilling.Api.csproj
Targetnet10.0 / linux-x64
Publishcomplete
Artifactsha256 verified
02Safe releases

Production changes without the cliff edge.

A release becomes current only after it starts successfully and passes its health check. Until then, the previous healthy version stays in place.

  • Configurable application health-check path
  • Immutable deployment history
  • Previous release preserved when readiness fails
  • One-command rollback to a retained release
  • Stable hostname across deployments and rollbacks
billing-api / deployments
v18

Deployment v18

Current · 2 min ago

v17

Deployment v17

Ready · rollback available

v16

Deployment v16

Ready · retained

Production changes only after readiness passes.
03Managed runtime

The infrastructure disappears, not the control.

BlackSails provisions and operates the runtime behind a private control plane. You keep the useful controls—secrets, logs, usage, and release history—without owning the plumbing.

  • Automatic HTTPS on Black Sails and verified custom domains
  • Environment secrets kept out of build artifacts
  • Branded deployment logs in the CLI and dashboard
  • Runtime health monitoring and guarded recovery
  • Per-application infrastructure isolation
  • Suspend, resume, archive, restore, and audited deletion controls
billing-acme.apps.blacksails.sh

Public edge

HTTPS ready

Runtime

Healthy

Secrets

4 configured

Isolation

Application scope

04Cost control

Know the rate. Set the ceiling.

Compute is usage-based, local builds are free, and connected Runnable builds carry no extra BlackSails build-minute charge. Every workspace has a hard spending limit, with a warning before workloads reach the cap.

  • $5 Hobby and $20 Pro monthly minimums become included usage
  • Metered CPU, memory, egress, and artifact storage
  • Hard spending limit controlled by the workspace owner
  • Warning at 80% of the configured limit
  • Usage and billing status visible in the dashboard
workspace / usage

Current cycle

$12.42

of $25 limit

CPU

$6.10

Memory

$5.82

Egress

$0.31

Artifacts

$0.19

Your next .NET service is one command away.

Bring an ASP.NET Core project. BlackSails handles the release, runtime, and production URL.