Case Study

EZYACCESS — Multi-Tenant Remote Support SaaS

A SaaS control platform for authorized remote support, session management, access control and usage-based licensing.

Status: Internal testing

Screenshots shown here use an isolated portfolio demo with fictional data. No production systems were accessed.

Portfolio demo: The screenshots use an isolated environment with fictional data. Live remote desktop sessions are disabled in the portfolio environment.

Product Development Web Applications

Product landing — Product framing for authorized remote access, sessions, and billing

Problem

Support organizations need a controlled way to manage technicians, customers, remote-support access, sessions and concurrent usage without exposing the underlying infrastructure directly to customers.

Solution

EZYACCESS is a product/control layer around remote-support infrastructure. It owns tenants, users, RBAC, support codes, guest access, devices, session lifecycle, concurrent slot limits, and administrative controls. MeshCentral remains the remote-desktop transport in production rather than a customer-facing system.

Key Features

• Multi-tenant organizations with server-side role visibility (Owner, Admin, Agent)
• Technician support codes: hashed 6-digit codes bound to an organization
• Guest/customer portal so the customer can verify a code without creating an account
• Device inventory for Windows and macOS endpoints
• CONNECT gating against the organization’s concurrent connection-slot plan
• Session creation, state, history, and an in-process session sweeper
• Plan catalog with slot limits (Starter 5, Professional 10, Business 15, Enterprise 20)
• Owner/admin controls including users, plans, and audit

Technology

Next.js React TypeScript PostgreSQL Prisma RBAC MeshCentral

Technical Architecture

EZYACCESS is a Next.js App Router application with PostgreSQL/Prisma for SaaS state (tenants, users, devices, support codes, sessions, and plans). Authorization is enforced on the server and does not trust client-supplied organization IDs. In production, MeshCentral is used as the remote-desktop engine through a control-layer integration; EZYACCESS is not a from-scratch remote-desktop protocol. The project includes approximately 195 unit tests.

Challenges

• Turning a remote-control engine into a billed multi-tenant product with roles, codes, and session records.
• Letting customers join a support session without an EZYACCESS or MeshCentral account.
• Enforcing concurrent connection slots rather than billing by session minutes.
• Keeping the public case study honest: the portfolio demo runs the real control plane with fictional data and does not show a live desktop.

Who This Is For

MSP and support teams that need attended remote access with tenant isolation, technician roles, and concurrent usage limits.

Outcome

The public case study shows the SaaS control plane: tenants, technician workflow, guest code entry, plans, and session history. The product is in internal testing. Live remote desktop sessions are not shown here.