Skip to content
Built in publicOpen by defaultTrust + adoption

Open-source foundationsbehind PyColors.

PyColors is built as an ecosystem: UI system, tokens, starters, and developer tooling — designed to help you ship real SaaS faster with predictable foundations.

Open-source is the foundation layer of the PyColors open-core strategy. Premium products exist to accelerate execution, not to create lock-in.

Open coreDocs-firstShipping weeklyStable foundationsPremium path stays clear

Why open-source

Open-source is a trust layer, an adoption path, and the foundation of the PyColors open-core strategy.

Trust

See the foundations. No black boxes, no vague promises — predictable primitives and product surfaces you can inspect.

Adoption

Clone, run, and evaluate quickly. Start with the open layer before deciding whether premium acceleration is worth it.

Velocity

Production-shaped foundations reduce guesswork. You ship faster and keep consistency as the product grows.

Open-core strategy

The ecosystem is open-source first. Commercial layers exist to accelerate execution, not to blur ownership or licensing boundaries.

TransparencyOpen foundations → paid accelerationAdopt progressively
Open-source (available now)Premium acceleration (planned / evolving)
PyColors UI + Tokens
Stable primitives, semantic theming, and docs-first usage.
UI PRO
Premium product patterns and higher-level SaaS surfaces.
Starter Free
A real SaaS surface with mocked data — built to validate UX fast.
Starter PRO
Auth, billing, backend foundations, and deployment guidance.
Developer tooling
Shared linting and TypeScript configs to keep codebases aligned.
All-In Access
The premium long-term path for builders who want the full ecosystem.

The goal is simple: inspect the foundations openly, adopt progressively, and upgrade only when the next layer creates real leverage.

Public repositories are governed by their respective repository licenses. Premium products, commercial access, private releases, and brand assets remain subject to separate commercial terms.

Repositories

Public repos you can clone today. Each one maps to a clear role in the ecosystem.

Foundations

UI, tokens, and tooling that power the ecosystem.

Core
Core foundations
UI + tokens
Core foundationsUI system
pycolors-ui

Documentation-first UI system built on semantic tokens and Radix primitives — optimized for real SaaS screens.

GitHub
Core foundationsTokens
pycolors-tokens

Semantic design tokens powering consistent theming across apps, templates, and starters.

GitHub
Developer tooling
DX
Developer toolingDX
pycolors-eslint-config

Shared ESLint configs for scalable TypeScript + Next.js codebases with strong defaults.

GitHub
Developer toolingDX
pycolors-typescript-config

Shared TypeScript configs to keep projects strict, predictable, and aligned as they grow.

GitHub
Products

Runnable entry points and the public website.

Adoption
Starters
Main entry point
StartersFree
pycolors-starter-free

Frontend-only SaaS starter demo: auth UX, dashboards, CRUD patterns, settings, billing surfaces, and admin UI — mocked by design, ready to wire.

GitHub
Website
Marketing + docs
WebsiteSite
pycolors-marketing

The marketing + docs site (Next.js + Fumadocs) — public mirror of the ecosystem website.

GitHub

Recommended path

Start with open foundations, validate the starter surface, then move to premium access only when leverage matters.

UI → foundationStarter Free → validate UXAccess → premium path

Built in public. Shipping weekly.