Separate the platform from the interface.

VijiTek Console is a developer cloud platform with its own web interface. Its repository separates the platform API, console backend, Nuxt interface and client SDKs. This case study describes those documented boundaries and the authentication workflow, rather than treating planned features as shipped capabilities.

ASP.NET Core · Nuxt · PostgreSQL · Redis · OpenIddict

Explore the project

A modular API with a separate console

The platform is organized as a modular monolith. The console has its own ASP.NET API and Nuxt frontend, while reusable clients live alongside them. This structure provides explicit integration points without requiring every module to become a separately operated microservice. It also makes the console a consumer of platform capabilities rather than the only place those capabilities can be accessed.

Keep identity at the gateway

OpenIddict hosts identity on the gateway. The console starts an OAuth authorization-code flow with PKCE and redirects users to the identity interface. After authentication, it exchanges the returned code for tokens. The console API validates JWTs through the .NET authentication client. Keeping the identity interface at the gateway gives external clients the same entry point as the first-party console.

Make client integration reusable

The repository includes a TypeScript authentication client for PKCE and a C# client for JWT validation and token helpers. Shared clients reduce the need for each application to reimplement the protocol. They still require correct audience, redirect and environment configuration: packaging a client does not remove the application’s responsibility to validate its integration.

Make startup steps explicit

The documented development setup starts PostgreSQL and Redis, then runs database migration and seed steps before launching the APIs and interface. Backend builds run sequentially to avoid shared DLL locks. These details are useful because they turn a collection of projects into a reproducible developer workflow. Production release and recovery procedures need their own validation; a local startup guide is not evidence of production reliability.

Separate implemented boundaries from future work

The architecture provides a basis for extending platform services and delivery workflows. A case study should distinguish code and documented behavior from a roadmap. For another project, we would first define the platform consumers, authentication requirements and operational ownership, then choose the smallest set of boundaries that supports them.

Plan your next project

Explore our software development services