Built in publicOpen-coreTrust + adoption

Open-source foundations behind PyColors.

PyColors is built as an open-core SaaS ecosystem: UI system, tokens, starters, and developer tooling designed to help developers ship credible SaaS products faster.

Open-source is the foundation layer. Premium products exist to accelerate execution when auth, billing, delivery, and production wiring become the bottleneck.

Open foundationsDocs-firstWeekly shippingFree → Pro path

Why open-source

Open-source is the trust layer of PyColors. It lets developers inspect the foundations, adopt progressively, and upgrade only when premium acceleration creates real leverage.

Trust

See the foundations. Inspect the primitives, tokens, tooling, and starter structure before you commit.

Adoption

Clone, run, test, and evaluate quickly. Start with the open layer before choosing a paid path.

Velocity

Production-shaped foundations reduce repeated setup work and keep your product direction coherent.

Open-core strategy

The ecosystem stays clear: open foundations for adoption, premium acceleration for builders who want to move faster.

Transparent modelOpen foundations → paid accelerationAdopt progressively
Open-source foundationPremium acceleration
PyColors UI + Tokens
Stable primitives, semantic theming, and docs-first usage.
Premium product surfaces
Higher-level SaaS patterns, starters, and production-focused assets.
Starter Free
A runnable SaaS surface with mocked data — built to validate UX fast.
Starter Pro
Real auth, Stripe billing, protected app structure, delivery, and backend foundations.
Developer tooling
Shared ESLint and TypeScript configs to keep projects aligned.
Future premium layers
Blocks, templates, stronger SaaS foundations, and commercial acceleration.

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

Repositories

Public repositories you can inspect, clone, and use today. Each one maps to a clear role in the PyColors ecosystem.

Foundations

UI, tokens, and tooling that power the ecosystem.

Core
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 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
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
WebsiteSite
pycolors-marketing

The marketing + docs site built with Next.js and Fumadocs — public mirror of the ecosystem website.

GitHub
Recommended path

Start open. Validate fast. Upgrade when it matters.

Use PyColors UI as the foundation, Starter Free to validate the product surface, and Starter Pro when real authentication, billing, and protected app architecture become the bottleneck.

UI → foundationStarter Free → validationStarter Pro → business layer

Built in public. Shipping weekly.