enomem
Self-hosted GitHub Actions runners on Azure: an Azure Functions handler in your subscription starts one Spot VM per job. enomem is licensed software that runs single-use GitHub Actions runners on Azure Spot VMs in your own subscription, suited to Azure-based teams that want a flat monthly fee.
Overview
enomem runs GitHub Actions jobs on Azure Spot VMs in your own subscription. Its enomem setup CLI creates a GitHub App and deploys an Azure Functions app, Key Vault, storage account, VNet and managed identity. When GitHub sends a queued-job webhook, the function creates a resource group with one VM that has an ephemeral OS disk and no inbound access, the runner takes exactly one job, and the resource group is deleted afterwards.
Jobs pick a size with a label alias such as enomem-8vcpu, with overrides for VM size, spot and cache. Runners use Ubuntu 24.04 LTS on x64 or ARM64, and a timer re-provisions on-demand when a spot deployment fails or stalls. The Team tier boots a stock image with cloud-init, while Enterprise adds pre-built images. Licences are flat monthly fees and Azure bills the VMs. The site does not name the company behind the product.
Notable
- The three posts on the enomem blog are all dated 28 April 2026.
- Runner images are rebuilt biweekly, according to the configuration page (checked 2026-11-22).
- The site footer carries a 2026 copyright and no launch announcement is published (checked 2026-11-22).
enomem specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux |
| Architectures | x64, arm64 |
| Deployment | Runs in your cloud or on your hardware · Self-hostable |
| Where it can run | Azure |
| Isolation | Each job gets a fresh Spot VM with an ephemeral OS disk in its own resource group, which is deleted when the job completes |
| Fresh environment per job | Yes |
| Hardware | Azure D-, E- and F-series sizes that support ephemeral OS disks, on AMD x64 and Cobalt ARM64. |
| Performance (vendor claim) | Not documented |
| Runner sizes | Built-in aliases from 2 to 32 vCPU on x64 and 2 to 16 vCPU on ARM64 (D-series, 4 GB per vCPU); any Standard_* size with ephemeral OS disk support can be used, up to 96 vCPU / 384 GB |
| Caching | A cache sidecar redirects actions/cache to Azure Blob Storage in your region, shared across the organisation’s repositories. Docker layer caching is documented through a pre-configured Buildx builder with cache-from and cache-to. |
| Docker layer caching | Yes |
| GPU | Not documented |
| Concurrency | Team: up to 50 concurrent runners; Enterprise: unlimited concurrent runners |
| Job limits | Resource groups older than 4 hours are deleted by a cleanup timer |
| Static IPs | Not documented |
| SSH into running jobs | Not documented |
| Observability | Application Insights logging and monitoring is deployed with the stack. |
| Setup | Install the enomem CLI, activate a licence key, run enomem setup to create a GitHub App and deploy the Azure resources, then set runs-on: enomem in your workflows. |
| Example label | enomem |
| Pricing | Free: $0 for personal projects, open source and non-commercial use. Team: $25/month or $300/year, up to 50 concurrent runners. Enterprise: $125/month or $1,500/year, with pre-built VM images and unlimited concurrent runners. Azure Spot VM costs are paid directly to Azure. |
| Free tier | Free licence for personal projects, open source and non-commercial use, with unlimited runners |
| Compliance | Not documented |
| Regions | Any Azure region that supports the chosen VM sizes, selected at setup |
| Open source | Not documented |
| Company headquarters | Not documented |
Facts from enomem’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- You run on Azure and want GitHub Actions runners inside your own subscription, VNet and region
- You want each job on a single-use Spot VM in its own resource group, with on-demand as a fallback
- You prefer a flat monthly licence, or qualify for the free non-commercial licence
- You need ARM64 runners on Azure Cobalt sizes
- You want actions/cache and Docker layer caches stored in your own Azure Blob Storage
Trade-offs
- Windows and macOS are not currently supported
- On the Team tier a stock Ubuntu image is used and cloud-init takes 45 to 55 seconds before steps start; pre-built images are Enterprise only
- The Team tier is limited to 50 concurrent runners
- The operating company, its location and terms of service are not documented on the site
Good fit for: Teams on GitHub Actions that already use Azure and want per-job Spot VMs inside their own subscription for a flat monthly licence.
Use cases enomem fits
- Lower CI cost: Runners use Azure Spot VMs billed per second by Azure, with a flat monthly licence from enomem.
- Docker builds: A pre-configured Buildx builder supports Docker layer caching with cache-from and cache-to.
- ARM64 builds: ARM64 aliases run on Azure Cobalt D-series sizes from 2 to 16 vCPU.
- Your own cloud: The webhook handler, cache and every runner VM are deployed in your own Azure subscription.
How enomem compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| enomem | GitHub Actions | Linux, x64, arm64 | Your cloud or hardware | Azure VM | $25/mo licence + Azure cost | 96 vCPU / 384 GB | Yes | Not documented | Not documented | Not documented |
| Managed DevOps Pools | Azure Pipelines | Linux, Windows, x64 | Platform-hosted | Azure VM | $15/month per parallel job + Azure VM cost | Not documented | Not documented | Not documented | No | United States |
| RunsOn | GitHub Actions | Linux, Windows, x64, arm64 | Your cloud or hardware | EC2 instance | €300/yr licence + AWS cost | 896 vCPU | Yes | Yes | No | France |
| Cirun | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Your cloud or hardware | Cloud VM | $29/mo (3 private repos) + cloud cost | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| Sprinters | GitHub Actions | Linux, x64, arm64 | Your cloud or hardware | EC2 instance | $0.01/job + AWS cost | 384 vCPU / 3072 GB | Not documented | Not documented | No | Germany |
| HyperEnv for GitHub Actions Runner | GitHub Actions | Linux, x64 | Your cloud or hardware | EC2 instance | $0.002/min fee + AWS cost | 192 vCPU / 768 GB | Not documented | Yes | No | Germany |
| WarpBuild | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Ephemeral VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Not documented |
| Actions Runner Controller (ARC) | GitHub Actions | Linux, Windows | Self-hosted | Kubernetes pod | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | United States |
| GARM (GitHub Actions Runner Manager) | GitHub Actions, Forgejo/Gitea Actions | Linux, Windows, x64, arm64 | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Romania |
Head-to-head: enomem vs Managed DevOps Pools
Frequently asked questions
What is enomem?
Which CI systems does enomem work with?
How does enomem isolate jobs?
Is enomem open source?
How much does enomem cost?
How do you set up enomem?
enomem.Does enomem have a free tier?
Does enomem support ARM64 runners?
Does enomem cache Docker layers?
How many jobs can run at once on enomem?
Where do enomem runners run?
What are the alternatives to enomem?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
CI Runners. (2026). enomem. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/enomem/