BotVeta — App Hub Automation Platform
Multi-tenant control plane to schedule, run, monitor, and scale RCM automation — bots, batches, workflows, audit, and integrations — behind JWT RBAC.
Problem
US Healthcare RCM operations run many Python automation bots across Eligibility Verification, Prior Authorization, and Claims. Each bot was managed separately, making it difficult to schedule, monitor, assign ownership, and scale as a multi-tenant product.
- No single place for instance lifecycle, schedules, or run logs
- Hard to coordinate batches and multi-step workflows
- Weak org-scoped RBAC and operational auditability
Solution — App Hub / BotVeta
Built BotVeta as the App Hub automation platform: a .NET control plane, React operator portal, and Next.js admin console.
- Operator portal: dashboards, bot instances, library + access requests, batches, timezone-aware workflow schedules, integrations (Twilio), Audit Center (process templates, copy-process, response review)
- Backend: JWT auth (OTP, Google, org switch), Hangfire cron jobs, run-now + conflict checks, workflow step executor, app-request / usage APIs
- Admin console: organizations, users, grants, bot catalog, HTTP logs, PDF & Slack ops, Product Weekly Update board pack
Architecture
Operator UI
wor-frontend — React 19 + Vite, org-scoped apps & RBAC nav
Control plane
wor-backend — .NET 9 Web API + Worker, Hangfire + SQL Server
Admin UI
apphub_admin — Next.js tenant/user/app/bot governance
Downstream products
BFF proxies to FastAPI AI PDF + Slack tracker with forwarded JWT
Secrets & ops
Azure Key Vault, Serilog, async HTTP request logging
What I Built
- Multi-tenant bot instance CRUD, assignees, schedules, run history
- Batch + workflow orchestration with trigger conflict checking
- Audit Center queue, work-item updates, time logs, CSV export
- Permission-aware navigation and route guards across App Hub products
- Admin surfaces for bot library, org onboarding, and grant editing
Impact
Centralized coordination for production RCM automation — roughly 40–60% less manual coordination — while keeping org RBAC, durable scheduling, and clear seams to AI PDF and Slack products.