Phaseo stands on open-source software, thoughtful design work, and dependable infrastructure. This page recognizes the projects and teams that materially shape what we build.
The foundations behind Phaseo's web experience and interaction language.
The declarative component and state model underlying Phaseo's interactive product surfaces.
How Phaseo uses it. Chat, model comparison, settings, observability, and every stateful interface are composed as React components.
The application framework that joins server rendering, routing, metadata, caching, and client interaction.
How Phaseo uses it. The public catalogue, authenticated workspace, API bridges, and this page all share one App Router application.
A utility-first styling system that keeps visual decisions close to the components they affect.
How Phaseo uses it. Responsive layout, typography, color, motion, and dark mode are expressed through a shared set of design tokens and utilities.
Open component patterns and accessible headless primitives that provide strong behavior without prescribing the final visual design.
How Phaseo uses it. Dialogs, menus, tooltips, buttons, selectors, and keyboard interactions throughout Phaseo build on these foundations.
A consistent, readable icon family with a broad vocabulary for product interfaces.
How Phaseo uses it. Icons clarify navigation, model actions, request status, settings, and compact controls where text alone would be cumbersome.
Created by Jakub Antalík
A family of carefully tuned canvas animations that gives background work a visible state without relying on a generic spinner.
How Phaseo uses it. Phaseo Chat uses the working state in the send and queue control, and the composing state while an assistant is preparing a response.
Projects that help Phaseo stream, render, and explain model output.
A Markdown renderer designed for incomplete text that is still arriving token by token.
How Phaseo uses it. Phaseo can render headings, lists, links, code, and mathematics while a response is streaming without waiting for the final document.
Streaming response
## A reliable gateway
Route by health, price, and capability
A TextMate-compatible syntax highlighter that renders code with editor-quality grammar support.
How Phaseo uses it. Code in model responses remains legible across languages and themes, including during technical comparisons and debugging.
Infrastructure and services that help Phaseo operate reliably.
A global application platform spanning edge compute, durable coordination, storage, networking, and security.
How Phaseo uses it. Phaseo's gateway and supporting APIs use Workers and related services to execute close to users and coordinate long-running workloads.
A Postgres platform with authentication, storage, realtime capabilities, and developer tooling.
How Phaseo uses it. Phaseo relies on Supabase for account identity and durable relational data such as workspaces, usage, credits, and gateway configuration.
Deployment and application infrastructure optimized for Next.js and modern web delivery.
How Phaseo uses it. The Phaseo website is built, previewed, and served through Vercel while private APIs connect to the wider platform.
A small, standards-based web framework designed for modern JavaScript runtimes.
How Phaseo uses it. It provides routing, middleware, and typed request handling across Phaseo's Cloudflare Workers APIs.
Payment infrastructure for secure checkout, payment methods, invoices, and billing events.
How Phaseo uses it. Stripe handles the financial transaction layer when customers purchase and manage Phaseo credits.
Tools that help us understand releases, reliability, and product behavior.
An open product analytics platform covering events, funnels, session diagnostics, and feature behavior.
How Phaseo uses it. Phaseo uses measured product signals to understand reliability and improve flows without treating intuition as evidence.
A feature-management and experimentation platform for controlled product delivery.
How Phaseo uses it. Feature gates let Phaseo introduce changes gradually, compare outcomes, and recover quickly when a rollout behaves unexpectedly.
This is a maintained product acknowledgement, not an exhaustive software bill of materials or license notice. Package-level copyright and license terms remain with their respective projects.