vicode
Explore
Sign in

A product library for software, AI systems, demos, and documentation.

One place to open the product, understand the system behind it, and move into the right demo, docs path, or project page without losing context.

Browse current workRead platform docs

Current products and systems.

Voice tooling, encrypted transfer, studio systems, and installable AI products pulled into one product library.

Browse projectsOpen Codex Voice page

Hear Codex Voice come alive before you open anything else.

One live voice moment tells the story faster than a wall of explanation. Start talking, hear the reply, and feel the product instantly.

Source-backed local voice companion for Codex workflows.

One clean product frame, then clear links into the project page and docs when someone wants the deeper implementation story.

Open Codex Voice pageRead Codex Voice docs

Try Codex Voice.

Start talking and hear the product answer back in real time.

Ready to help with this Codex thread.

VICODE-WINDOWS

Large product surfaces first

The screenshot needs enough space to explain the product before supporting text starts competing with it.

Live controls stay on top

Links and demo actions should feel attached to the product frame instead of floating somewhere else on the page.

Proof sits next to context

A demo, docs path, and project page should all stay one click away from the same visual moment.

Browse the library by product, package, collection, or docs.

Projects stay central. Packages, collections, and docs should help someone move deeper into the right part of the library without competing with the product itself.

Browse all public work
ProjectDocs available

Codex Voice

Source-backed local voice companion for Codex workflows.

Read docsOpen Codex Voice
Collection4 items

Creative Workflow Automations

Automation tools for Adobe and design teams.

Open collectionBrowse collections
Package19

Vectors + PSD's

Selling pack

Open packageBrowse packages
ProjectDocs available

PairSend

Live encrypted handoff between two devices.

Read docsOpen PairSend
Collection4 items

Bug Bounty Ops

Solo bounty workflows, reports, and signal tracking.

Open collectionBrowse collections
ProjectDocs available

Northbridge

Toronto web design and development studio.

Read docsOpen Northbridge

Products, demos, and studio systems in one place.

Each entry should make the product clear fast, then point to the right project page, demo, or docs path without over-explaining the layout.

View builder profileRead platform docs

The same stack keeps showing up because the work keeps shipping the same way.

Across the current library, the same stack keeps repeating: React and Next.js for the product shell, TypeScript and Tailwind for the UI layer, Node runtimes behind the apps and services, LiveKit where voice needs to be proved live. That repetition is intentional. It keeps the product surfaces easier to read and the next step easier to understand.

React + Next.js

The public library, project pages, and docs stay in one readable shell instead of splitting the product story across disconnected sites.

3 projects in the current library

Browse React projects

Questions people usually ask about vicode

A quick read should help you understand what vicode is, what you can open right away, and where to go next.

Browse vicode docs

What is vicode, exactly?

vicode is a product library for software products, AI systems, demos, docs, packages, and installable tools. It is built to help you understand the work quickly, then open the right project, package, or docs path without digging around.

What should I open first?

Start with the project that matches what you want to explore. Each project page gives you the clearest view of what the product does, how ready it is, and whether you can try it, install it, or go deeper through docs.

Do packages and downloads live here too?

Yes. When something is installable, downloadable, or ready to use, vicode makes that path obvious. When it is still a showcase, a private build, or a custom setup, the page makes that clear too.

What if I want more detail before I decide?

That is where the docs, demos, notes, and build context come in. vicode keeps the proof close to the product, so you can go deeper without losing the thread.

Explore the products, follow the proof, and open the right next step.

Move from the homepage into a project page, the docs, a demo, or an install path without switching into a different story halfway through.

Explore live projectsRead platform docs
Browse packagesBrowse collectionsView the full catalog

vicode keeps the product page, docs path, packages, and collections in one readable public system so the work is easier to understand and revisit.

Resources
API + CLIPublishingExploreDashboard
Catalog

Real product surfaces should lead the page.

Start with the interface, then let people move into the project, the demo, or the docs from there.

PairSend homepage

Encrypted browser-to-browser handoff for text and files.

PairSend is a secure ephemeral transfer product built around live sessions, direct handoff, and hard expiry instead of cloud storage.

Visit pairsend.comOpen PairSend page
Northbridge homepage

A premium studio site built as a reusable web scaffold.

Northbridge combines a polished frontend, Fastify backend, and a stronger system for shipping premium studio work without starting from zero each time.

Visit northbridge.studioOpen Northbridge page
Codex Voice tooling screenshot

Voice-first coding companion with a narrow public demo and deeper desktop workflow.

The public surface proves the interaction loop quickly, while the broader product extends into the dock, worker, and thread-aware workflow behind it.

Open Codex Voice pageRead Codex Voice docs

TypeScript

Typed UI and product logic keep the library easier to evolve as projects, demos, and package surfaces keep changing.

3 projects using the typed frontend stack

Read implementation docs

Tailwind + shadcn

The interface system stays consistent across product pages, docs surfaces, live demos, and reusable sections.

3 projects using the same UI system

Read UI docs

Node runtimes

Next.js apps, Vite builds, workers, and backend services all sit inside the same product library without forcing one runtime model on every project.

3 products running on the same JS stack

Browse Node products

OpenAI

AI slots into the library where the product actually needs it, without taking over the whole story.

0 projects using AI features

Open AI products

LiveKit voice

Voice products can prove the interaction loop directly on the page before someone moves deeper into docs or implementation detail.

1 voice-focused project

Open voice products
ProjectsCollectionsKitsDocs

© 2026 vicode. A clearer way to present active work.

Designed by Northbridge Studio.