multi-tenant domain router

One domain in.
The right database out.

SCS Spider sits in front of the Silk City Solution platform. Every school keeps its own domain — Spider catches the request, resolves the tenant's SQL database source, and hands the user to the SCS Web App. No per-school deployments, one router for the whole web.

Read the architecture API reference

Registered domains

Active tenants

Requests routed

API clients

ONLINE

SQL Server 2012

how it works

Four hops from domain to data

A school domain points at Spider

DNS for epanel.rmscraj.edu.bd (and every other school domain) resolves to this application. Users browse to the address they already know.

The Host header is matched

Spider checks the incoming host against its tenant registry — a cached lookup, refreshed every 30 seconds, managed from the admin console.

The database source is attached

Each tenant maps to one database on the SCS SQL Server — rmsc_db_new, harimohanschool_db, and so on.

The user is redirected with an encrypted token

An HTTP 302 sends the browser to the platform with ?token=scs1.… — an AES-256-GCM payload carrying the full database source (server, database, credentials). Nothing guessable in the URL; tokens expire in 5 minutes.

# resolve a domain through the API
curl -H "X-Api-Key: scs_…" \
  "/api/v1/resolve?domain=epanel.rmscraj.edu.bd"

{
  "domain":       "epanel.rmscraj.edu.bd",
  "schoolName":   "Rajshahi Model School…",
  "databaseName": "rmsc_db_new",
  "sqlUser":      "…", "sqlPassword": "…",
  "redirectUrl":  "https://…?token=scs1.q1nA9X…"
}

capabilities

Built for the whole platform

⇄

Domain routing

Unlimited school domains routed to the right database source with a single wildcard deployment.

{}

Documented API

Versioned REST API with Swagger/OpenAPI docs so any SCS app can resolve tenants programmatically.

⌘

Admin console

≡

Request logs

Every redirect and API resolution is logged with domain, tenant, client IP and timestamp.

One domain in.The right database out.