Services

Per-service documentation for every pulse-* service and ai-agents that runs on the PLANA platform.

Audience

PLANA staff, integration partners.

What's documented

Service	What
pulse-account	Customer account portal (Nuxt 3) at my.planapulse.ai
pulse-account-api	Backend behind every BOS / account-portal call (Fastify)
pulse-portal (BOS)	BOS frontend SPA (Vue 3 + Vite)
pulse-events	CloudEvents bus over Redis Streams
pulse-banking	PSD2 connector for 10 Bulgarian banks
ai-agents	Runtime for the 4 BOS agents

What's not yet documented in depth

The rest of the pulse-* family has shorter coverage in Reference → Repo map. Per-service pages will land as customers / partners ask for specific detail:

• pulse-auth — JWT + API key auth
• pulse-billing — Stripe subscriptions
• pulse-notifications — Email + in-app
• pulse-admin — Internal staff panel
• pulse-website — Marketing site
• pulse-data — Neural Business Network
• pulse-onboarding — Registration flow
• pulse-compliance — GDPR + 7-year audit
• pulse-automations — Workflow engine + n8n

How services fit together

       Customer browser
              │
              ▼
       Envoy Gateway
              │
   ┌──────────┼──────────────────┐
   │          │                  │
   ▼          ▼                  ▼
pulse-account  pulse-portal     Tenant Odoo
(Nuxt SSR)     (Vue SPA, BOS)   (Odoo workers)
   │          │
   └──┬───────┘
      │
      ▼
   pulse-account-api  ◀─────────  ai-agents
   (Fastify)                       (FastAPI + Anthropic)
      │
      ├──→ pulse-banking (PSD2)
      ├──→ pulse-events (bus)
      ├──→ pulse-billing (Stripe)
      ├──→ pulse-notifications (email)
      └──→ Tenant Odoo (XML-RPC)

The pattern: one Fastify (pulse-account-api) at the centre, fanning to specialised services. The frontend never talks to anything except pulse-account-api. The agents run alongside, called from the same API.

Where to read more

• Repo map — every repo at a glance
• Tech stack — what each service is built with
• API index — every endpoint, collated
• Architecture → Envoy Gateway — how requests reach each service