Internal QEdge Dev Team

QEdge Work Status

Master datasource, identity and access registry, and internal API surface for the QEdge platform ecosystem.

Environment: Dev

Service URLs

Human/Admin
https://qedge-work-dev.qedge.cn
Backend API Service
https://work.qedge.cn
Payload Admin
https://qedge-work-dev.qedge.cn/admin

Runtime

App
qedge.work
Mode
dev
Runtime port
3007
PM2 app name
qedge-work-dev
Database name
qedge_work_dev
Database host
121.40.90.70
Auth
Microsoft Entra internal SSO
Internal API auth
x-qedge-work-api-key header

Current Capabilities

  • Microsoft Entra internal SSO
  • Payload admin
  • qedge.work master datasource collections
  • qedge.vip data migration
  • /api/me
  • /api/access
  • /api/internal/resolve-access
  • stable backend API service via work.qedge.cn

Data Model

  • Accounts
  • Users
  • Identities
  • Memberships
  • Platform Access
  • Tenants
  • Properties
  • Services
  • Projects
  • Product Modules
  • Module Instances
  • External System Mappings

Recent Updates

  • qedge.work datasource foundation completed
  • QEdge seed script completed
  • Microsoft Entra SSO completed
  • qedge.vip migration completed
  • duplicate QEdge account fixed
  • qedge-work dev deployed
  • internal access resolver API added

API Contract

GET /api/me

Browser SSO session required. Returns current signed-in user and identities.

GET /api/access

Browser SSO session required. Returns current signed-in user, identities, memberships, platform access, tenants, and properties.

POST /api/internal/resolve-access

Server-to-server only. Requires x-qedge-work-api-key. Body: { "email": "user@example.com", "platform": "qedge_vip" }.

Integration Rules

  • qedge.vip and qedge.one should call qedge.work APIs.
  • Do not connect qedge.vip/qedge.one directly to qedge_work_dev Postgres.
  • qedge.work owns account, identity, membership, platform access, tenant, and property registry.
  • qedge.one owns product control plane.
  • qedge.one runtimes own runtime execution data.