Skip to content

Infrastructure

One node. Real capacity checks. No marketing fiction.

We run a single Pterodactyl node in India today. We would rather show you exactly what that means than pretend to have a global network.

India node

wings.crystalink.cloud · Pterodactyl + Wings + Docker

Primary
Location
India (IN)
Game panel
Pterodactyl 1.x, HTTPS
Daemon
Wings with TLS, Docker isolation
Play addresses
Allocations on the node's public IP
Free plan
1 GB RAM, hibernates when idle
Paid plans
Unlocked per node headroom

Every order is validated against the node's real advertised memory, disk and free allocation count before it can be placed. If the node cannot host your plan, checkout tells you instead of taking your money.

This is a single-node deployment: there is no automatic failover to another region. Planned maintenance and incidents are announced on the status page and by email.

Why some plans show as unavailable

A plan is orderable only when the node has free allocations and enough memory/disk headroom for it. This protects you from buying a plan that would immediately run out of resources.

Current integration readiness

Read from the live configuration - no secrets shown.

  • Pterodactyl Application API

    provisioning disabled

    Ready
  • Pterodactyl Client API (console/power)

    Ready
  • Cashfree payments

    sandbox + local test gateway

    Setup needed
  • Email delivery

    outbox-only (sending disabled)

    Setup needed

What runs where

LayerSoftwareResponsibility
Control planePterodactyl PanelServer runtime, users, allocations, installs
Node daemonWings + DockerContainer execution, SFTP, websocket console
Customer platformCrystalink (Next.js + worker)Accounts, plans, billing, provisioning, support
PaymentsCashfreeUPI, cards, net banking, refunds
EmailSMTP outbox workerVerification, invoices, lifecycle mail