Generate & Ship

From approved schemas to .NET or Node.js microservices, admin portal, GitHub Actions, Cloud Run URLs — and a local Docker stack when you want to run before you ship.

Code generation

Generate APIs with .NET or Node.js per module — Stack choice

APIs with .NET 10 & Node.js

Generate per-module APIs — .NET 10 with Dapper repositories, or Node.js 22 / NestJS with TypeScript. Parameterized SQL for PostgreSQL, MySQL, or SQL Server. Choose CQRS + Mediator or Service pattern per module.

.NET 10

Node.js

Docker

QuickCode DSL

Custom operations in DBML Notes compile to REST endpoints, handlers, and SQL queries on the stack you chose.

Postman collections

Auto-generated collections per module with auth environments for local, Docker, and Cloud Run.

Dapper + parameterized SQL

.NET modules use Dapper repositories and parameterized SQL for PostgreSQL, MySQL, or SQL Server.

EF Core migrations

Schema changes drive migration scripts so environments stay aligned with the DBML you approved.

NSwag clients

Generated clients help portals and services call module APIs with typed contracts.

Live Report Print and export — Print & export

Media columns list with preview — Media list

Admin Portal & Identity

An admin portal is generated as MVC source code in your project, not a hosted QuickCode SaaS panel. It includes CRUD for your tables, Live Reports from DSL Query operations (including Print & export with column layout and PDF/CSV), group-based authorization, table-level permissions, and configurable endpoint workflows. Declare BLOB_IMAGE, BLOB_PDF, BLOB_VIDEO, and BLOB_FILE columns in DBML to get upload fields, list actions, and in-app preview (image lightbox, PDF iframe, HTML5 video). Files are stored as HTTPS object URLs (Azure Blob, S3-compatible storage such as Cloudflare R2, or local files in development), not binary in the database. IdentityModule handles users, roles, and API/portal access; do not duplicate it in your modules.

Table management

Manage records through auto-generated portal screens tied to your DBML tables.

Access control

API method grants and portal page permissions from centralized management screens.

File and media columns

Use BLOB_IMAGE for photos and logos, BLOB_PDF for datasheets, BLOB_VIDEO for product or intro videos, and BLOB_FILE for other documents. The portal generates upload controls, size limits, and Preview actions without custom UI code.

Object storage backends

Configure Azure Blob Storage, any S3-compatible provider (including Cloudflare R2), or local file storage for development. The same pipeline applies to all BLOB_* column types.

Live Reports

DSL Query operations appear in the portal as Live Reports. Set parameters, click Run Report, and scan the result grid. The matching GET API path is shown on the page. Use Print & export to choose columns, set % widths, reorder fields, then download PDF/CSV or print with a live page preview.

Dynamic menus & permission groups

Portal navigation and permission groups follow your modules. LIST / DETAILS / INSERT / UPDATE / DELETE grants apply at page and API level.

Ops screens

Health, Swagger, and logging/ops entry points ship with the generated portal so day-two work starts in your repo.

Architecture

Microservices Architecture

Each domain module is a separate deployable API. YARP gateway routes client requests; an event listener service handles async processing where configured.

Gateway with YARP

Single HTTPS entry point to module APIs with routing and security.

Module APIs

Independent services per module, each with Swagger and Cloud Run deployment.

Ship

GitHub Repository & Actions

All generated code is pushed to github.com/QuickCodeStudio/{project-name}. GitHub Actions run tests, build Docker images, and trigger deployment workflows.

GitHub

QuickCode

Automated testing

Generated test suites for repositories and CRUD operations are included in the repo.

Confirm generate microservices — Generate

Deploy to Google Cloud Run

After you confirm Generate Microservices, QuickCode Studio tracks the full cloud pipeline: GitHub repo, code push, Google Cloud project, solution generation, migrations, then build and deploy for portal, gateway, listener, and each module API. URLs follow patterns like {project}-gateway.quickcode.net and {project}-portal.quickcode.net.

Cloud Run

Live pipeline in QuickCode Studio

Watch setup, generation, and Cloud Run deploy status in real time, including mid-run progress and the completed view with service links.

AI usage visibility

Open AI usage to see jobs and journeys by provider and model. Useful for demos, cost awareness, and explaining what the AI did for a project.

Regenerate safely

Re-run Project with AI or Generate Microservices when the plan changes. Confirm before existing modules are replaced.

Admin portal running in the local Docker stack — Portal

Run Locally with Docker

docker-compose in the generated repo runs the full stack locally (gateway, portal, module APIs, and databases) for development and demos before Cloud Run.

Try it

QuickCode Studio & Demo

Use QuickCode Studio for Project Analysis, DBML editing, ERD visualization, module AI, and the live Cloud Run generation pipeline. Explore the public demo (gateway, portal, GitHub) from the Demo menu, or start a new project from the homepage.

QuickCode Studio

https://studio.quickcode.net: projects, Project with AI analysis, per-module DBML, AI refine, and cloud generation progress.

Demo project

Live demo gateway and portal; see /demo-project for a guided walkthrough with credentials.

AI Rule Pack (Persistent)

Every generated project includes AI-readable guide files so code generation follows consistent project rules from the first prompt to the latest regeneration.

What is added: rule and guide files such as AGENTS.md and AI instruction files.
How AI uses it: the generator and AI assistants read these files before creating or updating code.
Why it is safe: regeneration preserves these files, so your generation behavior stays stable over time.