Documentation

How to use Excelso Pulse

Public guide: Excelso Pulse aggregates health and business signals from your backends and shows them in one dashboard.

Next.js · MongoDB · Auth.js

  • Health & Business Pulse

    A compact JSON contract your product API exposes so operations can read status, latency, errors, and KPIs in one round-trip.

  • Secrets at rest

    Bearer tokens are encrypted with AES-256-GCM before MongoDB storage; the browser never sees them again after save.

  • Aggregator

    The web app fetches every registered pulse URL in parallel, with caching and timeouts, then normalizes several payload shapes.

What is a pulse?

Typical backend route

GET …/internal/pulse

Each backend can expose a small JSON pulse (Health & Business Pulse) so operations sees latency, uptime, errors, and business KPIs in one response. Libraries such as excelso-pulse-express help you implement it on Express.

Excelso Pulse stores source metadata and encrypted Bearer tokens in MongoDB, then aggregates every registered URL on the server and renders the portfolio dashboard after you sign in.

Apps tab

After signing in, open Apps (/dashboard) to see all registered sources as cards. Tap a card for details, edit, or delete. Use Refresh in the toolbar to pull the latest data. Use Account for profile, password, and company or freelance name; Custom alerts in the sidebar defines rules per project.

Registering a source

Use “New source” (toolbar on desktop, button next to refresh on mobile) and provide slug, backend pulse URL, and Bearer token. Tokens are never shown again after save.

Optional app URL adds a quick link to the public front-end from the sheet.

Skipy — Excelso ecosystem

Skipy is an open-source web multi-tool for developers, QA, DevOps, and IT: secure password generator, JWT encode/decode, Base64 and URL encoders, fake data, JSON/YAML tools, short links, QR codes, and more — with a public API and the skipy-devtools-cli package.