RedWire
GitHub
The company

A company for
the open wire.

RedWire is an independent software company building browsing infrastructure that people can run themselves. We ship source, publish the trade-offs, and keep the network small enough to trust.

Founded2026
Products09
LicenseAGPL-3.0
ModelSelf-hosted
What we believe

Small surface.
Open source. Owned by you.

The most useful infrastructure is boring, inspectable and replaceable. We build tools that can be forked, deployed and shut down without asking anyone for permission.

Principle 01

Self-host first

Every product ships with a deployment path. If we disappeared tomorrow, your instance would keep running.

by design
Principle 02

Read the source

No opaque binaries, no hidden relay. The whole request path is a few files you can audit in an afternoon.

AGPL-3.0
Principle 03

Measure honestly

No synthetic uptime, no vanity numbers. Beacon reports what your browser can actually reach, from where you are.

browser-side
Principle 04

No ads, no accounts

Nothing to sign up for, nothing to monetise. The products are the software and the documentation.

zero telemetry
How we're organized

One network.
Two workshops.

RedWire is the company and the network. RRedwire is where the source lives. OGsWorkshop is the product studio behind it.

Company

RedWire

The network, the brand and the reference deployments. Owns the roadmap and the release process.

Companyred-wire.org
Source

RRedwire

The GitHub organization. Every product, workflow and deployment manifest lives here under AGPL-3.0.

Engineeringgithub.com/RRedwire
Studio

OGsWorkshop

The product studio behind Infrared and the original experiments that became RedWire.

Studiogithub.com/OGsWorkshop
Roadmap

Now, next, later.

Statuses are honest. Anything marked planned has no date attached.

Now shipping

Make the core excellent

  • Redline 1.0reference
  • RedArcadelive
  • Infraredlive
  • Signal manifestkit
  • RedKitdocs
  • Beaconlive
Next building

Connect the network

  • RedRelay relayplanned
  • Fleet configdesign
  • RedOS betawip
  • RedKit packageplanned
Later horizon

Make it boring

  • Managed hostingresearch
  • Mobile shellsresearch
  • Team workspacesidea
  • Public postmortemsalways
Security & transparency

What a relay
can and can't see.

Redline terminates Epoxy TLS at the destination. The relay forwards encrypted streams, so payloads stay encrypted in transit — but metadata is still metadata, and we won't pretend otherwise.

  • SeesDestination host, connection timing, byte volume and duration. Not page contents.
  • Doesn'tLog request bodies, credentials or browsing history by default.
  • DisclosureReport issues in the Discord or by email. We aim to acknowledge within 72 hours.
  • HardeningPin the lockfile, terminate TLS at the edge, rate-limit public relays, keep logs short.
relay — metadatadefault
# what the relay records
destination   example.com:443
transport     epoxy / wisp v2
payload       encrypted — not inspected
duration      12.4s
bytes         84,201 up / 1,204,882 down

# what it does not record
history       none
cookies       none
accounts      none

# recommended for public relays
$ MAX_CONNS=200 RATE_LIMIT=30/s
Changelog

What shipped.

Public, append-only and written by hand.

RedWire v0.1

Site, Redline reference proxy, Signal link hub, RedKit client, Beacon status and the Discord update log.

RedArcade + Browse

Four original browser games and a browsing service page for Infrared and Redline.

Redline hardening

Docker, Fly and VPS deployment paths, a no-store worker config and a WISP relay smoke test.

Infrared

The flagship proxy, maintained with OGsWorkshop. The product that started the network.

Contact

Talk to
the wire.

Deployment help, security reports, partnerships or a game you want in the arcade. The Discord is the front door.

Join the Discord Email
RRedwire source OGsWorkshop studio Beacon status Documentation deploy