↗ OpenActions
Log inCreate account
Building in private beta

Your workflows.
Your infrastructure.

Open-source runners for GitHub Actions. Run on infrastructure you control, with a managed cloud service in development.

Join the private beta See how it works
Free account signup. CI access opens as workspaces are provisioned.

Product preview · Illustrative data, not live customer results.

↗ Linux-first execution
⌘ Familiar workflow tools
◷ Clear run history
≋ Monthly plans + usage
Built for the work between commits

Less friction.
More forward motion.

Your CI should help you move. We’re building OpenActions around the parts that make every development loop easier.

Compute with purpose

A Linux runner platform tuned around CPU performance, local storage, and the builds your team actually runs.

A clearer view of every run

The CI engine tracks job status, queue time, execution duration, and logs. Customer workspaces are the next step.

Pricing you can plan around

Our planned model pairs a monthly minute allowance with a published overage rate. Signup is free while billing is being prepared.

A familiar starting point

Your code.
Your workflow.
Your choice of runner.

OpenActions starts with the CI tools teams already use. GitHub workflow support lives in the underlying engine; customer onboarding is being built around it.

01

Create your OpenActions account

Choose a workspace name and get your account ready.

02

Connect when your workspace opens

Repository and runner setup will follow workspace provisioning.

03

Build, review, repeat

Run history and usage will come together in your workspace.

.github/workflows/ci.ymlEngine example
name: Build & test
on: [push, pull_request]

jobs:
  test:
    # Existing Kiln runner label
    runs-on: kiln
    steps:
      - uses: actions/checkout@v4
      - run: npm ci
      - run: npm test
      - run: npm run build
Illustrates the existing engine. Customer runner labels and repository connection become available after provisioning.
Pricing, with room to grow

A monthly plan.
A clear next minute.

Included compute for everyday work. Overage for the weeks when you’re shipping more.

Proposed launch pricing.
Plans are not yet available to purchase.

Proposed plan

Starter

For side projects and small teams.

$19/ month
10,000 compute minutes included

Then $0.003 per compute minute

Join the private beta
  • Monthly included allowance
  • Published overage rate
  • Linux-first CI workspaces
Proposed plan

Team

For teams building every day.

$49/ month
25,000 compute minutes included

Then $0.003 per compute minute

Join the private beta ↗
  • A larger monthly allowance
  • Published overage rate
  • Linux-first CI workspaces
Proposed plan

Scale

For a heavier build schedule.

$149/ month
80,000 compute minutes included

Then $0.0025 per compute minute

Join the private beta
  • Our largest planned allowance
  • A lower overage rate
  • Linux-first CI workspaces

One compute minute represents one minute on a 2-vCPU Linux runner. A 4-vCPU runner uses two compute minutes per minute; an 8-vCPU runner uses four. The planned meter counts execution time, not queue time. Prices are in USD and remain subject to change before launch. Creating an account does not start a subscription.

Before you get started

A few things
to know.

A clear view of what’s here today and what’s coming next.

What can I use today?

You can create an OpenActions account, sign in, and view your account workspace. Customer repository connections, CI execution, and usage billing are still being prepared.

Do I need a credit card?

No. Account signup is free, checkout is currently disabled, and joining the beta does not create a paid subscription.

Does OpenActions replace GitHub Actions?

The existing engine can provide runners for GitHub Actions. OpenActions’s customer service is being built on that foundation. A standalone workflow platform is a longer-term goal.

Is OpenActions open source?

The self-hostable engine is licensed under Apache 2.0. We’re preparing the public OpenActions release alongside the managed cloud beta.

Can I run macOS or Windows builds?

The current execution platform is Linux. Native macOS and Windows runners need separate infrastructure and are not part of this beta.

Are the dashboard numbers real results?

The landing-page dashboard is an illustration using sample data. We are benchmarking the underlying engine separately and are not claiming a universal speed improvement.

Your next build starts here.

Create your account and be ready for your workspace to open.

Join the private beta