forkalope

Forkalope / For business

Git hosting
without the seat tax.

A familiar code forge for teams that want a managed service without giving one company permanent control of their infrastructure.

Apply for the pilot See the options

The pricing principle

Hire another developer.
Your Git bill doesn’t change.

Forkalope plans are designed around the service you use, not the number of people on your team. Unlimited members means your developers, designers, contractors, bots, and occasional collaborators can share one forge without a new seat charge for each account.

We still have to price the things that cost money to operate: repository and artifact storage, compute, bandwidth, CI runners, recovery replicas, retention, regions, and support. A larger bill should reflect more capacity or more service—not a head-count tax.

This is the pricing direction we’re taking into the business pilot. Exact limits and rates will be published before a paid plan opens.

01 / Choose your operating model

Same software.
Different responsibility.

Free software

Run it yourself

Clone the open-source project, run it on your own infrastructure, and keep every part of the deployment under your control.

Unlimited members. Your capacity, your cost.

View the source
Managed

Forkalope operates it

We handle hosting, updates, backups, monitoring, migration, and support while your team uses a GitHub-shaped workflow.

Unlimited members. Pricing is planned around storage, compute, recovery, and support.

Dedicated / BYO

Your account. Our operations.

Your company rents the infrastructure or gives us an approved account to operate. You keep the provider relationship and a clear path to take over.

Unlimited members. Capacity is sized to your deployment and requirements.

02 / What we would run

The work around
the forge.

Migration

Move repositories, issues, teams, and automation with a plan for the parts that usually get missed.

Operations

Updates, backups, capacity, monitoring, incident response, and a human who knows your deployment.

Recovery

Approved nodes can participate in the shared recovery network, with replicas and drills agreed in the service plan.

Exit

Export your Git data and take over infrastructure you control. Leaving should be a planned handoff, not a rebuild from scratch.

03 / Early access

Help shape the first business plan.

We’re looking for teams who are tired of outages, per-seat pricing, or infrastructure they can’t take with them. Pilot conversations will help set storage, support, recovery, and pricing commitments around real use.

This is an invitation to talk, not a live service or uptime guarantee.

Start a pilot conversation Read the pricing FAQ