Skip to content

A FOUNDATION FOR YOUR NEXT PRODUCT

Your product. A stronger start.

Bring your website, application and backend together. Start with thoughtful foundations, keep clear boundaries and make room for the product only you can build.

  • TypeScript throughout
  • Server-rendered interfaces
  • One Nx workspace
visomi / workspace
V
WORKSPACE / 01 OR

Your workspace

Everything in its place.

Project overview

Ready to build

Latest activity

The foundation is in place.

Make it yours

Bring your own domain, workflows and ideas.

Explore this interface
pnpm nx serve web-app
An example of what you can build

PURPOSEFUL TOOLS. ONE SHARED FOUNDATION.

  • Nx
  • Angular
  • Astro
  • Express
  • PostgreSQL
  • Tailwind

01 / THE FOUNDATION

Less setup. More product.

The everyday essentials deserve the same care as the features that make your product different.

A home for every experience

An Astro website, an Angular application and an Express API, each with a clear responsibility.

Website · Product · Backend

Identity from the start

Passkeys, account verification and durable sessions provide a backend foundation for trusted access.

Passkeys · Sessions · Account security

A shared visual language

Native controls, typed Tailwind recipes and consistent themes make both interfaces feel like one product.

Angular + Astro · Native HTML

02 / HOW IT FITS TOGETHER

Connected by design. Clear by responsibility.

Keep public content, product interactions and business capabilities in their own place. Compose them as the product grows, with explicit runtime boundaries.

See the complete picture
The runtime mapHTTP / SSR
Express gateway

Owns HTTP composition, startup and process resources.

Website

Astro SSR

/en/ · /es/

API

Express

/api/

Independent SSR application

Angular SSR

Gateway integration is next
/app/en/ · /app/es/

03 / MADE TO FEEL LIKE ONE PRODUCT

Good defaults, down to the details.

Readable typography. Clear feedback. Native controls. A shared set of visual recipes connects Angular and Astro without bringing an application runtime to your website.

37component families to explore

Browse the components

Workspace preferences

A small example, using the real components.

button.classes({ variant: 'secondary', size: 'sm' });

04 / YOUR FIRST STEPS

From repository to running locally.

Install the workspace, choose an entry point and explore the stack at your own pace.

Follow the setup guide
  1. 01

    Get the source

    Start from the repository and its documented conventions.

  2. 02

    Install once

    One dependency manifest and one lockfile for the workspace.

  3. 03

    Explore locally

    Run the website, then the application and gateway.

visomi-stack / terminal
pnpm install --frozen-lockfile
pnpm nx serve web-site

ROOM TO GROW

A foundation for what comes next.

A product needs more than screens. The architecture leaves space for background work, live experiences and client-protected content as those capabilities evolve.

Architecture direction · See implementation status in the architecture guide.
  • 01

    Background work

    Long-running tasks with a dedicated execution boundary.

  • 02

    Realtime experiences

    Authorized updates delivered to the right client.

  • 03

    Protected content

    A direction for client-owned keys and encrypted data.

A few things worth knowing.

Is Visomi Stack a finished product?

It is a reusable foundation for building products. You bring the domain, product experience and deployment choices. The architecture guide distinguishes current capabilities from the direction of the stack.

Why Astro and Angular together?

Astro suits public, content-led pages. Angular provides a structured application experience. Shared visual recipes connect both while each framework keeps its own rendering and interaction model.

Can I use only the parts I need?

Yes. The applications and shared libraries have explicit responsibilities. Start with what fits your product, and use the repository guides to understand the dependencies and tradeoffs.

Where should I begin?

Start with the local setup guide. Explore the website, the component catalog and the application shell, then review the API and architecture documentation before adding your own domain.

Make the foundation yours.

Explore the decisions. Try the interfaces. Start building your product.