Pre-launch · founding waitlist now open · joining does not start a trial or take payment
ForgeOS course · pre-launch

Forge Your Own Operating System.

Build a UEFI-native OS from an empty file to a polished desktop, storage, networking and a source-audited DOOM port. Join the founding list now; choose whether to reserve an offer later.

  • No payment to join
  • No trial starts here
  • Unsubscribe any time
Founding waitlist

Get the launch email and reserve your preferred offer.

ForgeOS is not publicly launched. Your tier choice measures interest; it is not a purchase.

Consent is not pre-checked. We store your selection and campaign source, prevent duplicate contacts, and email a confirmation. No purchase event is recorded.

The project is real

You’ll study the system that already exists.

This is a real ForgeOS interface reference from the project source archive—not a stock dashboard mock-up.

ForgeOS desktop showing the native terminal and text editor
ForgeOS desktop showing the native terminal, text editor and file manager
ForgeOS desktop captures from the actual build. Course footage and lessons use the same build path.
What students will build

Not a toy kernel. A system you can see, use and debug.

Start with modern firmware, own the framebuffer and memory map, then add the subsystems that turn boot code into an operating system.

01 · BOOT

UEFI entry and pixels

Build the toolchain, load directly from firmware, understand the hand-off and render correctly into the framebuffer.

02 · KERNEL

Memory, interrupts and panic diagnostics

Own the memory map, timers and keyboard input, then build the real ForgeOS panic screen and contain user-process faults without taking down the kernel.

03 · DESKTOP

Compositor and windows

Implement double buffering, dirty regions, text, controls, draggable windows and a coherent desktop.

04 · STORAGE

USB and filesystems

Read and write real files, load assets and move beyond a desktop that only exists in memory.

05 · NETWORK

A connected OS

Bring up Ethernet and build the network layers needed for connected ForgeOS applications.

06 · DOOM

Port a real application

Integrate doomgeneric callbacks for display, input, time and files using a legally obtained compatible WAD.

Founding-member offers · pre-launch

Choose your level of build access.

Joining the waitlist reserves your preference. Stripe Checkout is a separate step. There is no artificial quantity cap or countdown.

Starter

Normal price $9/month

$0 first month

$0 for your first month, then $9/month after launch

  • All current written lessons
  • Future written course updates
  • Desktop-to-DOOM build instructions
  • No source or section downloads

Recurring billing: Stripe requires a payment method and creates a subscription with a free trial through the first month after launch. You pay $0 today. After the trial it charges $9/month until cancelled.

Lifetime

Normal price $149 once

$49 once

$49 founding-member price · one-time payment

  • All current and future written ForgeOS course lessons
  • All approved current module, source and section downloads
  • Future major ForgeOS course section packages
  • Permanent account restoration and course updates
  • Excludes unrelated future products, one-to-one support and third-party commercial game data

One-time payment: Stripe charges $49 once. This is not a subscription and there are no recurring fees. Access covers the ForgeOS course and inclusions listed above.

Exact deliverables

Know what “access” means before you choose.

ForgeOS is pre-launch, but the current course build and package boundaries are concrete. Founding members receive early access only after verified Stripe Checkout.

WRITTEN COURSE

Seven core modules

Boot to pixels, memory and interrupts, compositor, windows and desktop, USB and filesystems, networking, and Run DOOM.

GUIDED ROADMAPS

Four advanced sections

Native runtime and applications; storage, hardware and performance; networked desktop; virtualisation and compatibility.

BUILDER FILES

Section 1 build packages

Important-module archives, the Section 1 completion package, build assets, QEMU/USB tools and the verified DOOM integration patch.

LIFETIME FILES

Complete approved source set

Builder files plus current advanced-section packages, reconstructable ForgeOS source parts, hashes and future major course packages.

ACCOUNT

Multi-device restoration

Restore verified access by purchase email and a short-lived code. Manage recurring billing through Stripe’s Customer Portal.

NOT INCLUDED

Clear boundaries

No promise of one-to-one support, unrelated future courses or products, commercial WAD files, or universal compatibility with every physical machine.

Course roadmap

A staged path from firmware to a usable OS.

“Current build” means the material exists in the pre-launch course archive. “Guided roadmap” means the section teaches the implementation path without claiming every subsystem is a finished drop-in product.

01

Zero to desktop

UEFI toolchain, framebuffer, memory, interrupts, compositor and a draggable desktop.

Current build
02

Storage, networking and DOOM

USB mass storage, filesystems, Ethernet layers and application-port callbacks.

Current build
03

Native runtime and applications

Processes, user memory, ELF loading, syscalls, threads, services and native apps.

Guided roadmap
04

Hardware and performance

AHCI, NVMe, display modes, CPU capabilities, memory pressure and profiling.

Guided roadmap
05

Networked desktop and compatibility

TLS, ForgeWeb, packages, VMX capability and staged hosted-emulation foundations.

Guided roadmap
Founder story and project proof

Built after hitting the walls tutorials leave out.

“I detached UEFI’s own USB driver mid-boot and the firmware started spamming write errors. I hit a 64 KB DMA boundary that silently corrupted transfers. The UI ran in QEMU and black-screened on real silicon. ForgeOS turns those failures into the lesson path.”
— ForgeOS founder · project source and build evidence retained with the course
the bug the emulator hides
// PixelsPerScanLine != HorizontalResolution
// QEMU may forgive this; physical panels will not.

buf[y * pitch + x] = colour;   // correct
buf[y * width + x] = colour;   // sheared output

// Treat hardware claims as measured evidence:
if (wc_policy_validated(fb_base, fb_size))
    enable_write_combining(fb_base, fb_size);
FAQ

The pre-launch details, plainly.

Is ForgeOS launched?

No. This is the pre-launch founding waitlist. The current course build exists, but the public launch has not happened. Waitlist members will receive the launch timing and founding-access path by email.

Does joining the waitlist charge me or start a trial?

No. A waitlist signup is recorded as a lead, not a purchase. It does not create a Stripe customer, start a trial, take payment or grant course access.

What happens after I join?

You receive a branded confirmation email showing your selected tier. You can then choose whether to continue to Stripe Checkout when that tier’s checkout is available. Your founding offer is honoured according to the tier you selected.

How do the Starter and Builder trials bill?

Both are recurring subscriptions and require a payment method in Stripe Checkout. You pay $0 through the first month after launch, then the saved payment method is charged $9/month for Starter or $39/month for Builder until cancelled. ForgeOS sends a transactional reminder before the trial ends.

How do I cancel a trial?

Use “Manage subscription” on the ForgeOS access page to open Stripe’s Customer Portal and cancel before the displayed trial end. ForgeOS sends a transactional reminder before billing. You can also email support@access.jirt.net.

Is Lifetime really one payment?

Yes. The founding price is $49 once. It is not recurring. Lifetime means permanent access to this ForgeOS course, its current approved downloads, future written lesson updates and future major ForgeOS course section packages. It does not include unrelated products or one-to-one consulting.

Do founding members get access before public launch?

Waitlist members do not. A founding member who completes verified Stripe Checkout receives access to the current course build. Access is granted from server-verified Stripe state—not from the browser return URL alone.

What hardware is supported?

The supplied baseline is verified in QEMU/OVMF. The course teaches bounded tests on compatible UEFI hardware and how to record the exact machine and EFI hash. It does not promise universal physical-hardware compatibility.

Pre-launch · no payment to join

Start with an empty file. Start here.

Tell us what you want to build and which founding offer genuinely interests you. We’ll send the launch details—no fake countdown, no surprise charge.

Join the ForgeOS waitlist