RunMyJob rebrands as RunJob and adds Spike Instances for European CI

RunMyJob has rebranded as RunJob and moved to runjob.eu, positioning the company as an independent European CI infrastructure provider. The platform says its new Spike Instances offer per-second, load-based billing for GitHub Actions and GitLab CI jobs, with the goal of lowering cost without sacrificing performance.

Why it matters: - RunJob is pitching a different model for continuous integration in Europe: faster runners, pricing tied to actual usage and infrastructure it owns and operates. - The shift could matter for teams that want more control over where CI workloads run, how much they cost and how much data leaves Europe. - The company says the approach removes the usual trade-off between performance and cost for compute-heavy CI jobs.

What happened: - RunMyJob announced a rebrand to RunJob and a move to runjob.eu. - The company said the change reinforces its commitment to independent, high-performance CI infrastructure for Europe. - RunJob provides cloud runners for GitHub Actions and GitLab CI. - RunJob said customers pay only for the resources their jobs actually use.

The details: - Spike Instances™ are KVM-based virtual machines built to handle workloads of different sizes without requiring customers to choose a machine type in advance. - On the Business plan, each job can use up to 48 vCPU and 96 GB of memory. - CPU and memory load are measured independently every second. - Customers are billed for actual consumption rather than allocated capacity. - Idle CPU is free. - RunJob says this load-based billing model changes the economics of CI. - The company owns and operates its physical infrastructure in European Tier III data centers. - Every job starts in a clean, isolated KVM environment with an ephemeral filesystem that is erased after completion. - RunJob is SOC 2 Type II compliant. - Existing GitHub Actions and GitLab CI configurations remain compatible. - For larger GitHub Actions migrations, the open-source GitHub Workflows Assistant can replace runs-on labels across multiple repositories and branches, letting teams review changes before committing them. - RunJob also offers S3-compatible Flexible Persistent File Storage for caches, artifacts and datasets between jobs. - The platform supports Docker-based builds, GitHub Actions cache, GitLab cache and shared persistent directories. - Depending on the workload, RunJob says CI jobs can run up to two times faster and at up to one-fifth of the cost of conventional cloud runners. - The company is available at runjob.eu. - RunJob also linked to its LinkedIn page and X account.

Between the lines: - RunJob is positioning itself against hyperscale cloud resellers by emphasizing owned hardware, European data centers and transparent billing. - The rebrand and new domain signal a broader identity shift from a product name to a Europe-focused infrastructure platform. - The messaging suggests RunJob is targeting teams that care about sovereignty, compliance and predictable CI spend.

What's next: - RunJob will likely use the rebrand to push more adoption of its Spike Instances and European infrastructure story. - GitHub Actions users with larger migrations may use the Workflows Assistant to move workloads more quickly. - The company appears to be betting that lower-cost, higher-performance CI will pull teams away from conventional cloud runners.

The bottom line: - RunJob is trying to make European CI cheaper, faster and more controllable by tying pricing to real usage and running its own infrastructure in Europe.