Skip to main content

🌐 Site Architecture

Overview​

Vartovii uses a unified domain architecture:

sentryanalytic.com              β†’ Landing (docs_site React app)
β”œβ”€β”€ /app                        β†’ Dashboard (React)
└── /api/docs                   β†’ Swagger API documentation

docs.sentryanalytic.com         β†’ Technical documentation (Docusaurus)
β”œβ”€β”€ AI Agent
β”œβ”€β”€ Features
β”œβ”€β”€ Crypto Module
β”œβ”€β”€ API Reference
β”œβ”€β”€ Deployment
β”œβ”€β”€ Scrapers
└── Reports

Public developer docs are served from knowledge-base/. The marketing landing site remains a separate surface in docs_site/, even when both are edited in the same repository.

Sites & URLs​

URLPurposeSource
sentryanalytic.comLanding page (info, roadmap, features)docs_site/
sentryanalytic.com/appDashboard applicationdashboard_app/
sentryanalytic.com/api/docsSwagger API documentationFastAPI auto-generated
docs.sentryanalytic.comTechnical documentationknowledge-base/

Landing Page (sentryanalytic.com)​

Beautiful React + Vite landing page with all product information.

Source: docs_site/​

Tech Stack​

  • Framework: React 19 + Vite
  • Styling: Tailwind CSS
  • Animations: Framer Motion
  • Stats: react-countup

Sections​

  • Hero with CTAs
  • Modules Showcase (Corporate + Crypto)
  • Features Overview
  • AI Analysis
  • Tech Stack
  • Roadmap
  • Founder Story
ButtonDestination
πŸš€ Dashboard/app
πŸ“š Documentationdocs.sentryanalytic.com
πŸ”Œ API Reference/api/docs

Dashboard (/app)​

Main application for company analysis.

Source: dashboard_app/​

Features​

  • Company Search
  • Trust Score Analysis
  • Battle Mode
  • AI Chat (Π’Π°Ρ€Ρ‚ΠΎΠ²ΠΈΠΉ)
  • Crypto Intelligence
  • Reports & PDF Export

The dashboard runtime enters through the router-first path main.jsx -> RouterProvider -> router.jsx -> DashboardLayout. Internal cleanup of unused legacy shells does not change the public dashboard URL structure or feature surface. Frontend API traffic flows through shared helper modules in src/utils/http.js and src/utils/api.js, which keep request formatting and error handling consistent across dashboard features. Long-running collection and report-refresh flows use status-aware backoff polling instead of fixed hot-loop timers, reducing redundant background requests while data is still pending. Export and rich-rendering dependencies also load lazily, so PDF, markdown, and chart-heavy tooling are deferred until a user actually opens those feature paths. The dashboard runtime also keeps user-facing status visible in the UI rather than emitting direct debug-console noise during normal production flows. The active dashboard runtime also no longer carries the legacy axios client; request formatting and transport flow through the shared frontend HTTP helpers. Core AI-assisted report and analysis paths also keep their evaluation coverage visible in CI, while future telemetry and research enhancements can evolve behind the same stable public dashboard routes. Cross-surface forensic journeys now also preserve lightweight session continuity between the Farcaster mini app and the main dashboard, so a user who opens a full report from a mini app scan stays within one consistent analytics funnel. This continuity is based on product interaction metadata, not on legal, investment, or employment guarantees. Dashboard report interactions now use the same telemetry backbone, which keeps report-open, refresh, rerun, export, and share actions inside the same product-observability contract instead of relying on isolated logs. The Farcaster mini app bridge now also uses a pinned tested SDK version rather than a floating CDN alias, reducing unexpected client-runtime drift across dashboard-handoff flows. The dashboard shell also reads runtime version metadata from the live backend instead of relying on a hardcoded local badge. Corporate PDF downloads now enrich the renderer with a structured Deep Research workflow payload for entity brief, agent workflow, forensic/corporate fusion, confidence, and action-plan blocks without changing the public report JSON response shape. The same dashboard shell now also exposes an alert panel for entity-scoped score-change subscriptions and watchlist notes as part of Alert System Beta.

Technical Documentation (docs.sentryanalytic.com)​

Docusaurus 3.7 documentation platform.

Source: knowledge-base/​

Tech Stack​

  • Framework: Docusaurus 3.7
  • Search: Algolia DocSearch
  • i18n: English, Ukrainian, German
  • Hosting: Cloud Run (europe-west1)
  • CI/CD: GitHub Actions

Features​

  • βœ… Full-text search via Algolia
  • βœ… Multi-language support (EN, UK, DE)
  • βœ… AI-powered translations (Gemini 3 preview + 2.5 fallback)
  • βœ… Automatic deployment on push
  • βœ… Custom domain with SSL
  • βœ… v4-compatible markdown hooks configuration for broken markdown link handling

API Documentation (/api/docs)​

FastAPI auto-generates Swagger/OpenAPI docs.

The current public trust-score API surface also exposes explicit rate-limit headers plus cursor-based search pagination, stable sort parameters, and freshness metadata without requiring a separate route family beyond /api/v1. The same active /api/v1 routes also keep one canonical error payload across their 400/404/429/500 paths.

Sections​

  • Scraping Endpoints (job start, progress, control)
  • Company Endpoints
  • AI Chat & Feedback Endpoints
  • Agent Tool Endpoints (search, trust score, company listings)
  • Crypto Endpoints
  • Analytics Endpoints
  • Reports Endpoints

Deployment​

ServicePlatformRegion
Backend + Dashboard + LandingCloud Runeurope-west4
docs.sentryanalytic.comCloud Runeurope-west1

The active production data layer now runs on managed Neon PostgreSQL under the same public application URLs. This infrastructure change does not alter public feature routes or API contracts on its own.

Auto-Deploy​

  • knowledge-base/** changes β†’ GitHub Actions β†’ Cloud Run (docs)
  • Backend changes β†’ Manual gcloud deploy or GitHub Actions

Documentation Sync​

LocationPurposeConsumers
docs/Internal architecture, implementation, governanceInternal engineering
docs_site/Landing pageMarketing, users
knowledge-base/Public technical documentation and API referencesDevelopers, integrations

Documentation Publishing Rule​

  • Public documentation covers public-facing product and technical surfaces only.
  • Internal sprint execution notes, admin diagnostics, and operational cleanup details remain in docs/.
  • Internal sprint transitions and repository refactors do not change public feature or API commitments on their own.
  • Public docs should use legally safe wording and avoid promises of guaranteed safety, outcomes, or verification.
  • Public docs describe runtime behavior at the API/feature level, while repository-level DB hardening details remain in internal documentation.
  • Documentation publishing remains CI-validated before release so public references stay synchronized with the approved product surfaces.
  • The AI assistant keeps one stable public chat contract even as the internal runtime evolves through shared routing, prompt, tool, and model adapter layers.

Public API Docs Scope​

  • Public API docs cover documented public endpoints and reference usage.
  • Internal/admin operational endpoints are intentionally excluded from the public documentation contract.

Last updated: March 14, 2026