JumpStart AMS
Overview of JumpStart AMS, the Cosmos-backed application management support portal
consumerjumpstartamssupportcosmos
Updated 2026-11-03
Verified 2026-11-03
JumpStart AMS is a Cosmos-backed application management support portal for project-based support operations. It provides ticket intake, triage, routing, SLA tracking, knowledge management, AI assistance, dashboards, integrations, and project administration.
The app is implemented as two repos:
| Repo | Runtime | Owns |
|---|---|---|
jumpstart-ams-backend | FastAPI, Celery, Celery beat, PostgreSQL, Redis | Auth session, project context, AMS APIs, operational data, background jobs, Cosmos SDK integration |
jumpstart-ams-frontend | Next.js 16 App Router, React 19, Ant Design 6 | Browser portal, admin screens, dashboard UX, API calls to the backend |
Users
| Role | Project role | Primary surfaces |
|---|---|---|
| End users | end_user | Ticket creation, own-ticket tracking, portal search, knowledge articles, virtual agent chat |
| Support teams | support_team | Ticket queues, assignment, comments, attachments, duplicate checks, AI insights, resolution notes |
| Support managers | support_manager | Routing dashboard, SLA at-risk view, operations dashboards, productivity reports, team leadership |
| AMS admins | support_admin | Teams, routing rules, source instances, import mappings, ticket form/status config, SLA policies, notification templates |
| Super admins | Cosmos superuser | Project onboarding, project activation, Cosmos resource binding, baseline seeding, user/project membership, Ticket Intelligence workspace |
Project roles are AMS project memberships; see Project Roles And Permissions.
Module Map
| Module | Notes |
|---|---|
| Tickets | CRUD, activities, bulk status/priority/assignment, follow state, chat links, portal stats |
| Knowledge | Article admin, portal search, known-error chat, KB generation, KB health scans |
| AI operations | Ticket insights, sentiment, code/config issue analysis, automation definitions, monitoring events |
| Routing and SLA | Rules, skills, assignments, calendars, definitions, escalation rules, recomputation |
| Integrations and imports | Source instances, connector tests, credential storage, sync logs, field mappings, ServiceNow-style import flows |
| Admin and audit | Portal/chatbot config, agents, prompts, roles/users, field config, audit logs, notifications |
Cosmos Dependencies
| Cosmos capability | AMS usage |
|---|---|
| User Service | OAuth2 PKCE login, token exchange, JWKS validation, live user identity |
| Python SDK | User-scoped and service-scoped Cosmos clients from backend sessions or service credentials |
| ADK | Virtual agent, ticket AI, analysis workflows, and model-backed operations through ADK V2 |
| Configurator | Agents, skills, collections, roles, and project resource binding through SDK clients |
| Storage and RAGflow | Attachments, project documents, knowledge search, and collection reindex operations |
Cosmos owns identities, organizations, OAuth clients, service credentials, and platform resources. AMS owns only the operational support data and project bindings needed for the portal.