How NoQue Works

A modern, cloud-native architecture designed for public service delivery at scale.

System Architecture

Cloud-Native

Built for the cloud from day one. Serverless architecture with auto-scaling and high availability.

PostgreSQL

Robust, scalable database with row-level security and multi-schema isolation for data protection.

POPIA Compliant

Built-in compliance with data residency, encryption, and audit logging requirements.

Technology Stack

  • Backend: Flask (Python) with RESTful APIs
  • Database: PostgreSQL with schema isolation
  • Frontend: Bootstrap 5 with responsive design
  • Authentication: OTP (SMS) and JWT tokens
  • Hosting: Vercel with South African data centers
Request Flow
Citizen
  ↓
Widget/Website
  ↓
NoQue API (Flask)
  ↓
PostgreSQL Database
  ↓
SMS Gateway → Confirmation

Intelligent Service Mesh

Dynamic capacity management and slot generation

Capacity Curves

Define how capacity changes throughout the day and week:

  • Peak hours with higher capacity
  • Off-peak hours with reduced staffing
  • Day-of-week variations
  • Special event adjustments
Closure Management

Automated handling of closures and holidays:

  • Public holidays
  • Planned maintenance
  • Emergency closures
  • Recurring closures
Service Availability

Configure service-specific operating hours:

  • Different services, different hours
  • Day-specific availability
  • Location-specific rules
  • Priority services
Load Balancing

Automatic distribution of bookings:

  • Even distribution across slots
  • Prevent overbooking
  • Real-time capacity checking
  • Pessimistic locking for accuracy

Booking Flow

1
Service Selection

Citizen browses available services and selects location and service type from the widget or website.

2
Slot Availability

System queries available slots based on service mesh rules, capacity curves, and existing bookings.

3
Authentication

Citizen enters phone number, receives OTP via SMS, and verifies to create/retrieve identity.

4
Booking Creation

System creates booking with pessimistic locking to prevent double-booking, generates reference number.

5
Confirmation

Citizen receives SMS confirmation with booking reference, date, time, and location details.

Security Architecture

Multi-Layer Security

Network Layer

TLS 1.3 encryption, DDoS protection, rate limiting

Application Layer

OTP authentication, JWT tokens, CSRF protection, input validation

Data Layer

Row-level security (RLS), schema isolation, encrypted connections, AES-256 encryption at rest

Audit Layer

Complete audit trail, immutable logs, admin action tracking

Learn More

For detailed security information, see our Security & Compliance page.

Integration Options

Embeddable Widget

One-line JavaScript integration

RESTful API

Full programmatic access

Admin Portal

No-code configuration

SMS Gateway

Automated notifications

Ready to See It in Action?

Try our live widget demo or explore the API documentation.

Try Widget Demo API Documentation