Demo Project

Open the demo in QuickCode Studio, then try the live sample it generates: a YARP API gateway with Swagger, an admin portal you can sign into, and the full project on GitHub.

QuickCode Studio
The same demo project opens in QuickCode Studio as a one-hour read-only tour. No account and no secret code.

Review modules, the schema, and Ask AI on the project that powers the live portal and gateway.

Open in Studio
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
Admin Portal
The admin portal provides auto-generated CRUD for your tables, group-based authorization, table-level permissions, and configurable endpoint workflows.

Use the Live Reports sidebar: pick a report, set parameters, click Run Report, and see the GET API path used for the call. From results, open Print & export to choose columns, set widths, reorder fields, preview pages, then download PDF/CSV or print.

ProductCatalog in the live demo includes BLOB_IMAGE, BLOB_PDF, and BLOB_VIDEO columns: upload files, preview PDF and video in a lightbox, and open files in a new tab. Storage works with Azure Blob, S3-compatible providers (e.g. Cloudflare R2), or local files for development.

Manage tables, roles, API access, and workflows without writing UI code.

Demo credentials:
Username: [email protected]
Password: String1!

Open Portal
QuickCodeStudio/demo on GitHub
Code Repository: GitHub
The generated demo stack lives in GitHub under QuickCodeStudio/demo, source, module layout, and GitHub Actions workflows for build and deploy.

View on GitHub

Microservices Architecture

Platform overview

The map mirrors a generated QuickCode system: entry at the top, core services in the middle, third-party integrations on the right, then event streaming and logging below.

  • Entry: Admin users hit the Admin Portal; Api users reach the API Gateway (YARP).
  • Core services: Identity & Access sits above generated modules. Every service is an Api paired with its own database — Gateway fans out to each API. Optional BFF orchestrates endpoint workflows across generated modules and external APIs.
  • Third party services: Module APIs talk to Third Party Api on the right via a shared horizontal trunk (HTTP).
  • Event streaming: Modules publish to Kafka; a Kafka Event Listener drives event workflows and a workflow store.
  • Logging: Gateway and services ship logs to Elastic Search; Kibana sits beside it for ops views.

Legend colors match the diagram: HTTP, Kafka, logging, and database links. Drag nodes on the map, or open fullscreen for a larger canvas.