Djengo

gRPC contracts

Edge hub

djengo-proto-contracts

gRPC documentation map

Browsers cannot issue raw HTTP/2 gRPC calls here. This page lists every backend package so you know what exists — host, port, proto file, and service names. Call them with grpcurl, BloomRPC, or Postman’s gRPC client against Docker DNS (e.g. profile-service:50051).

Example: grpcurl -plaintext profile-service:50051 list

profile.proto · profile-service:50051

Auth, users, staff, OTP, admin profile, security.

organization.proto · organization-service:50055

Orgs, companies, branches, roles, departments, SaaS billing.

admin.proto · admin-service:50057

Platform admin accounts, roles, action audit.

files.proto · files-service:50052

File upload and metadata.

address.proto · address-service:50053

Address CRUD for any entity.

communication.proto · communications-service:50054

Transactional email / OTP mailer (Nest).

comms.proto · comms-service:50061

Realtime chat / push (.NET) — also OpenAPI at /comms/docs.

financials.proto · financial-service:50056

Payroll, budgets, wallets, guest billing, procurement — OpenAPI at /financials/docs.

events.proto · events-service:50060

HR events stack — OpenAPI at /events/docs.

facility.proto · facility-service:50062

Layout & occupancy — OpenAPI at /facility/docs.

operations.proto · operations-service:50059

Reservations, F&B, kitchen, incidents.

Source of truth

Edit protos in backend/djengo-proto-contracts/proto/, then npm run sync:services. Gateway Swagger documents the HTTP surface that wraps many of these RPCs.