ARCHITECTURE / THE BIG PICTURE

One system. Clear boundaries.

A modular foundation gives each part a purpose. The gateway owns HTTP composition; your business capabilities own the behavior.

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/

What you can explore now.

Available today

Astro renders the site through the Express gateway, including localized routes, public assets and the component catalog.

Angular renders and hydrates independently, with localized builds, Signal Forms examples and a responsive shell.

The API includes passkeys, account verification, recovery and PostgreSQL-backed sessions. The product authentication screens are the next UI step.

Typed visual recipes power native Angular and Astro adapters. Each framework owns its composition and interaction.

Architecture direction

These examples describe the intended shape of the platform. They are not all implemented in this rebuild.

Mount the Angular application alongside the site and API, keeping composition separate from domain logic.

Give scheduled and long-running work a dedicated worker, with handlers owned by the relevant business capability.

Keep connection authorization and event delivery separate from HTTP requests and background execution.

Explore client-owned keys and encrypted envelopes. Security assumptions, recovery and production guarantees need explicit design and review.

Organize business capabilities around their domain. Keep genuinely cross-cutting concerns shared.

Importing an application does not open a port. The owning executable starts and closes process resources.

Nx targets, unit suites and browser checks verify behavior alongside the implementation.

Start locally, then follow the repository guides for runtime ownership and integration details.