The platform is built as a set of services designed for stable operations. The key idea is separation: a fast core API, dedicated auth, background ingestion, durable storage, cache, and eventing.
Web
Next.js public site (themes, discovery, blog, legal surfaces).
Admin
Next.js admin console with operator workflows.
Core API
Rust api-core: catalog APIs, SEO surfaces, sitemap generation, operational endpoints.
Auth service
Sessions, admin security posture, and access controls.
Worker
Ingestion + refresh jobs for providers and maintenance tasks.
Postgres
Primary datastore for catalog + configuration + audit.
Redis
Caching and performance posture.
NATS (JetStream)
Events/queue to decouple ingestion and operational flows.
Reverse proxy
TLS termination and routing (Apache/Nginx/DirectAdmin supported).
Topology
Internet
-> Reverse proxy (TLS)
-> web (public site)
-> admin (operator console)
-> api-core + auth-service
-> postgres / redis / nats
-> worker (ingestion)Operational principles
- Keep internals behind the reverse proxy.
- Separate public UX from operator workflows.
- Use background workers for ingestion and heavy tasks.
- Build SEO surfaces as first-class routes, not afterthoughts.
- Optional AI modules are deployment-controlled.
Why the core is written in Rust
- High concurrency with consistent response times for catalog and SEO endpoints.
- Memory-safety by design, reducing runtime failure classes in long-lived services.
- Better performance per vCPU for ingestion-heavy workloads and large sitemap operations.
- Lower resource overhead helps operators keep infrastructure costs more predictable.
See how the stack becomes a product
The admin console turns the stack into operator workflows: provider setup, SEO control, monetization, incident response.