Demo Project
Explore a live sample of what QuickCode generates: YARP API gateway with Swagger, an admin portal you can sign into, and the full project on GitHub—use the links below to try each part.
Gateway & Dashboard
Gateway Details:
Single entry point to demo module APIs with Swagger documentation.
Connected Modules:
Routed services and live OpenAPI docs for each module.
Health Checks:
Status indicators for gateway and downstream services.
Quick Links:
Portal, GitHub repository, and live API docs.
Open Gateway
Single entry point to demo module APIs with Swagger documentation.
Connected Modules:
Routed services and live OpenAPI docs for each module.
Health Checks:
Status indicators for gateway and downstream services.
Quick Links:
Portal, GitHub repository, and live API docs.
Open Gateway
Admin Portal
The admin portal provides auto-generated CRUD for your tables, group-based authorization, table-level permissions, and configurable endpoint workflows.
Manage tables, roles, API access, and workflows without writing UI code.
Demo credentials:
Username: [email protected]
Password: String1!
Open Portal
Manage tables, roles, API access, and workflows without writing UI code.
Demo credentials:
Username: [email protected]
Password: String1!
Open Portal
Code Repository — GitHub
The generated demo stack lives in GitHub under QuickCodeNet/demo—source, module layout, and GitHub Actions workflows for build and deploy.
View on GitHub
View on GitHub
Microservices Architecture
Platform overview
QuickCode targets a modular microservice layout: each bounded context becomes an API with its own database, fronted by a single gateway and optional admin UI—not a monolith with shared tables.
- Entry points — Admin users use the portal; external systems call APIs through the gateway (YARP).
- Identity — Central authentication service and dedicated identity store for users, groups, and tokens.
- Generated services — One deployable API per module, each with an isolated database (no cross-module DB coupling).
- Events — Kafka-backed listener coordinates workflows and cross-service reactions without tight synchronous coupling.
- Observability — Logs and metrics flow into Elasticsearch/Kibana for operations and troubleshooting.
- Delivery — Generated repos include CI/CD (e.g. GitHub Actions) toward container runtimes such as Google Cloud Run.
The diagram shows component types and data flow—not individual module names from a sample project.