Where Orbzz stands, honestly

The short version

Orbzz is early. This post exists so nobody has to guess what is real: here is what is built, what is in progress, and what is still only a specification.

What exists today

• The design system. Colour, spacing, radius, duration and motion tokens, with an automated contrast test over token pairs, a component library with light and dark states, and a Storybook to document them.
• Accounts and profiles, server side. Registration, email verification, sign-in with rotating refresh tokens, rate limiting, profiles with per-field privacy, and an image upload pipeline that strips metadata and re-encodes everything it stores.
• This website. A static export — no database, no analytics, no cookies.

That is genuinely it. It runs locally, it is tested, and it is not available to the public.

What is in progress

The web client for accounts, onboarding and profiles. It is the layer you would use to sign up once there is something to sign up for, and it is being built screen by screen against the real API rather than against mocks.

What is planned, not built

Orbs and channels. Messaging, threads and reactions. Circle connections and people search. Voice, video and rooms. Moderation tooling. Mobile and desktop apps. The public API and bots. End-to-end encryption. Billing. Every one of those is a phase in the project brief with acceptance criteria, and every one of them is currently a specification.

On this website, those features are labelled Planned or Coming soon. If you see a label that looks wrong, that is a bug worth reporting.

What we do not claim

No certifications — no SOC 2, no ISO, no GDPR certification. No uptime numbers, because there is no production uptime to measure. No user counts, because there are no users. No end-to-end encryption, because it is not implemented and has not been reviewed. No launch date we would have to walk back.

Why publish at all

Because the alternative is a landing page full of screenshots of a product that does not exist, and that is how you start a project with a credibility debt. If you want to follow along, the blog and the changelog are where milestones will land, and the contact page is where to reach us.