Early access

Stop renting compute you already own.

The PCs, Macs and Linux boxes around your office sit idle most of the week while you pay GitHub by the minute. Beehive puts them to work on your CI builds, and soon your apps, and steps aside the moment someone needs their machine.

  • Windows, macOS and Linux
  • Joins with one line
  • A tenth of GitHub's price
What would you run? Optional
How many machines? Optional

Medbill keeps your address only to email you about Beehive, never shares it, and deletes it if you unsubscribe or don't confirm it within a week.

How much would you save?

2,000 free minutes, gone by day 2. GitHub bills the rest.

You'd save

US$214 a month US$2,570 a year

GitHub's bill goes from US$288 to US$48. Beehive charges US$23 and the power costs about US$3.

How it's worked out

GitHub's Linux runners at US$0.006 a minute for 2 cores. Beehive charges a tenth of that, with its first 2,000 minutes a month free. Power at about 10 W a core and US$0.23 a kWh.

Busy 40 hours a week, idle the other 128

Outside working hours, the Windows PCs, Macs and Linux boxes around your office do nothing. Beehive puts those hours to work, and steps back the moment someone needs their machine.

Mon 12 am

Out of hours: everything left in the office works flat out. The laptop went home with its owner.

People at their desks: 40 hoursFree for Beehive: 128 hours

  • WindowsDesktop PCOffice desktopAll of it
  • macOSLaptopOffice desktopGone home
  • LinuxBuild boxAlways onAll of it

From one line to money saved

No servers to set up. Change runs-on to beehive in a workflow and the jobs that ran on GitHub's runners run on yours.

 
Installing the Beehive agent
Joined the Main hive as desk-07
8 cores, 16 GB: room for 2 jobs at once
Mon
Tue
Wed
Thu
Fri
Sat
Sun

Nights and weekends: all of it Work hours: a quarter

mini-1mini-2mini-3mac-studiodesk-04mini-4desk-07mini-5mac-minidesk-02mini-6laptop
Minutes off GitHub's bill50,000
Saved this monthUS$296
  • test (3 of 8) on desk-07, 7 minsaved US$0.08
  • build on mini-2, 4 minsaved US$0.05
  • e2e (1 of 4) on mac-mini, 12 minsaved US$0.14
  • lint on mini-4, 1 minsaved US$0.01
  • test (4 of 8) on desk-07, 6 minsaved US$0.07
Now

Run it by asking Claude or Grok

Connect your agent once and tell it what you want: add this computer, make a hive for the office desktops, find out why a machine is offline. It acts as you, with the role you give it, and you can take it away at any time.

Then ask: Add this computer to Beehive, Make a hive for the office desktops that only runs jobs outside work hours, Which machines are offline, and why?, What has Beehive saved us this month?.

Coming

Run real apps on your own hardware

Describe an app in one file and Beehive runs it on machines you already own: as many replicas as you ask for, spread across your offices, behind one address. Lose a whole office and the app keeps answering. Public addresses and custom domains come with Team and Enterprise.

# beehive.yaml
kind: Service
name: orders-api
image: ghcr.io/acme/orders-api:2.1.0
replicas: 3
spread: zones
port: 8080
health: /healthz
routes: 
  - public: orders.acme.com
orders.acme.comBeehive edge TLS, picks a healthy replica

Brisbane officePower cut

  • Linuxmini-1orders-api
  • macOSmac-miniorders-api
  • Windowsdesk-03orders-api

Sydney officePower cut

  • Linuxmini-2orders-api
  • Windowsdesk-11orders-api

Melbourne officePower cut

  • Linuxbuild-boxorders-api
  • Windowspc-21orders-api
  • Windowsdesk-24orders-api
Answered
0
Retried on another replica
0
Failed
0
Coming, with Windows

Every PC in the building, at once

For a fleet, nobody goes desk to desk. Add Beehive to Microsoft Intune once, assign it to a group, and every PC in it installs the agent and joins your hive by itself. On Enterprise, Beehive does the adding for you, gives each group of PCs its own profile, and lets go of any PC Intune retires.

Beehive Add machines, Intune
MSI
beehive-agent.msiWindows 10 and 11, x64 and Arm
Download
Key
Enrolment key for the Office desktops hivebee_enrol_7KQ2M9XPDT…
Copy
Cmd
Install command for Intunemsiexec /i beehive-agent.msi /qn ENROLMENT_KEY=bee_enrol_7KQ2M9XPDT…
Copy
Microsoft Intune Apps, Windows, Add a Win32 app
Microsoft Intune Beehive agent, Assignments

Required

  • Office desktops 48 devices
  • Meeting rooms 6 devices
  • Executive laptops 9 devices
Save
  • OFFICE-PC-01Waiting
  • OFFICE-PC-02Waiting
  • OFFICE-PC-03Waiting
  • OFFICE-PC-04Waiting
  • OFFICE-PC-05Waiting
  • OFFICE-PC-06Waiting
  • OFFICE-PC-07Waiting
  • OFFICE-PC-08Waiting
  • and 40 more

48 of 48 PCs in the hive

Safe on the machines people use every day

A job on someone's desktop can't see their files, and they never have to think about it. Work stays on hardware you own.

  • Jobs never see people's files

    Each job runs in a container of its own, with none of the machine's files, held to the share you set, and deleted when it finishes.

  • Nothing to open on your network

    The agent dials out to Beehive. There's no port to open and no VPN to set up.

  • Your code goes straight from GitHub

    Runners check out from GitHub and report back to it directly. Beehive's hub schedules the work; your code never passes through it.

  • Credentials that last one job

    Each runner's GitHub credential works for a single job and reaches it through its environment, never a command line someone could read.

  • You decide what runs where

    Admins choose which GitHub organisations' jobs each hive of machines takes, and how much of each machine they get.

  • Terminals need a fresh sign-in

    Opening a terminal on a machine needs an admin who signed in minutes ago, and every one is logged.

What it runs

Builds run on Beehive today. The rest is on its way, and the waiting list hears first.

Pay a tenth of GitHub's price

Only for the minutes your jobs run on Beehive. Idle machines cost nothing on any plan, however many you bring. Prices are in US dollars, with nothing added on top.

Questions

Do we have to manage the machines?

No. Install the agent once with one line, or roll it out to every PC with Intune. After that it keeps itself up to date in the maintenance window you choose, never in the middle of a job, and the portal shows each machine’s health and anything that needs a look. There’s no server for you to run: Beehive’s hub is hosted.

Do the machines need static IP addresses, open ports or a VPN?

No. Each machine dials out to Beehive over HTTPS, so anything that can reach the internet works: office Ethernet or Wi-Fi, behind your router, or a laptop on someone’s home network. No static IP, no port forwarding and no VPN.

What does a machine need?

A Mac or a Linux machine with Docker Desktop or Podman, and at least 7 GB of memory to give jobs; it runs as many 2-core, 6 GB jobs at once as fit, and you can size them per hive. Installing needs no admin rights. Windows PCs join at launch.

Will the people using them notice?

Not unless they look. Each machine follows a profile: the hours it may work and how much of it to use. It gives less while someone is at the keyboard, takes no new jobs while its own programs are busy or it’s on battery, and every job is held to its share of the processor and memory.

Do we have to change our workflows?

One line in each: runs-on: beehive. Jobs run in Linux containers, so docker, services: and Testcontainers work as they do on GitHub’s runners. Jobs that need a macOS or Windows runner stay on GitHub’s.

What if someone turns a machine off mid-job?

That job fails on GitHub, as it would on any runner that disappears, and a re-run puts it on another machine. Beehive stops sending work to a machine it can’t hear from, and profiles keep it rare: a laptop on battery takes no new jobs.

Is our code safe on someone's PC?

Each job runs in a container of its own with none of the machine’s files, and the container is deleted when the job finishes. Your code comes straight from GitHub to that container and never passes through Beehive’s hub. More under Safe on the machines people use every day.

Which CI services does it work with?

GitHub Actions today. GitLab, Bitbucket Pipelines and Azure DevOps are planned.

What does it cost?

A tenth of what GitHub would have charged for the minutes your jobs run on Beehive, and the first 2,000 minutes each month are free. Machines cost nothing for being in the hive, only for the work they do. Team, at US$19 a month, adds public addresses and custom domains for apps on your machines, with 50 GB of traffic a month through Beehive’s edge. Enterprise, at US$99 a month, connects Beehive to Intune and adds sign-in with Entra ID, with 500 GB. Traffic past either costs US$0.15 a GB. Neither plan charges per machine, and a year costs ten months. Prices are in US dollars, with nothing added on top.

Can we run Beehive ourselves?

Not yet. The hub is built to run on your own infrastructure as well as ours, and that’s planned for later.

Put the compute you already own to work

Join the waiting list and we'll let you know when there's a place for your hive.