Shipping In Public

Back To Home

Open Source

Public software we maintain to make our research, infrastructure, and operator-first thesis legible.

Why this page exists

We use open source as evidence, not ornament. Everything here demonstrates how Antigenic approaches tooling, infrastructure, and technical stewardship.

What We Publish

Selected open-source work that makes our operating standards legible.

Real tools that solve active internal or operator-facing problems.
Infrastructure patterns we want to make reproducible in the open.
Public repositories with named stewardship and clear review paths.

Flagship Tools

Operator-facing software with a clear product point of view.

These are the tools that best represent how Antigenic thinks about interface quality, engineering leverage, and public execution.

pAInt

active

A visual editor for localhost web projects. Inspect elements, edit styles, manage CSS variables, and export changelogs for Claude Code.

Built For

Frontend engineers and design-minded developers iterating on local apps.

Why We Built It

We needed a faster bridge between live UI experimentation and source-controlled implementation, especially in AI-assisted workflows.

TypeScriptNext.jsDeveloper ToolsClaude Code

Project Proof

Repository

View on GitHub

License

Apache-2.0

Jump To Setup

Infrastructure

Deployment patterns and systems work that support durable operations.

This work packages repeatable infrastructure decisions so operators can start from a reliable baseline instead of scratch.

DocuSeal Helm Chart

active

A production-ready Helm chart for deploying DocuSeal on Kubernetes.

Built For

Platform teams standardizing document signing infrastructure in Kubernetes environments.

Why We Built It

We wanted a repeatable deployment path for DocuSeal that operators can audit, configure, and run without custom chart work.

HelmKubernetesDocuSeal

Project Proof

Repository

View on GitHub

License

MIT

Stalwart Helm Chart

active

A highly opinionated, Stalwart mail server deployment packaged as a Helm chart for Kubernetes.

Built For

Platform teams running mail infrastructure on Kubernetes.

Why We Built It

We wanted a reproducible way to operate Stalwart in production without rebuilding deployment patterns from scratch each time.

HelmKubernetesMail Server

Project Proof

Repository

View on GitHub

License

MIT

Featured Project

pAInt

What you can do

  • Inspect and select any element in a live preview
  • Edit typography, spacing, layout, colors, borders, shadows, and gradients
  • Manage and reuse CSS custom properties
  • Work across breakpoints (Mobile, Tablet, Desktop)
  • Navigate through a DOM layers tree
  • Insert new HTML elements from the Add Element panel
  • Track every change and export a structured changelog
  • Send changelogs to Claude Code for source-file application

Getting started

Install

npm install -g @antigenic-oss/paint

Quick start

  1. 01Run paint start to launch the editor at 127.0.0.1:4000
  2. 02Start your target app (for example localhost:3000)
  3. 03Select the target localhost port in pAInt and click Connect
  4. 04Start inspecting and editing

Prerequisites

  • - Node.js >= 20.9.0 (global CLI)
  • - Bun >= 1.3 (local development)
  • - A localhost app running in development mode

Maintained by Antigenic

Developer:Jehcy Adorna
Reviewer:Larron

01

Project stewardship

Each project has a named maintainer and an accountable review path. Product and technical decisions stay close to the people shipping the work.

Major changes are proposed in public through the repository so rationale, review, and implementation history stay visible.

02

How to contribute

Contributions are welcome. Start with the repository issue tracker and follow the contribution guidance in each repository.

Fork the repo, open a focused branch, and send a pull request with clear context on the problem and the proposed change.

If you want to collaborate directly, reach out through the Antigenic Ventures team and we will route it to the right maintainer.