Hostinger Platform

"Shared hosting trades control for cost; VPS buys it back. Design around the plan's caps." [INFERENCE]

TL;DR

Deploys and operates applications on Hostinger — budget shared hosting and VPS — covering deployment (Git / SFTP / PM2 for Node), MySQL/MariaDB, auto-renewing SSL, and DNS/email via hPanel. The cost-floor leg of the Firebase + Vercel + Hostinger Platform Lens. [EXPLICIT]

When to use

• Deploying a static/PHP/Node app to Hostinger shared or VPS. [EXPLICIT]
• Running a persistent Node process with PM2 on a VPS. [EXPLICIT]
• Provisioning MySQL/MariaDB, SSL, DNS records, or email forwarding in hPanel. [EXPLICIT]
• NOT for serverless/edge workloads (use vercel-platform) or Firebase surfaces (use firebase-platform). [INFERENCE]

Sub-capabilities (resource map)

Procedure

1. Pick tier: shared (PHP/static, low connection caps) vs VPS (Node/daemons, root). [EXPLICIT]
2. Deploy via Git deploy or SFTP; for Node, run under PM2 with a startup hook. [DOC]
3. Provision DB in hPanel with a least-privilege user; pool/close connections (shared caps are low). [INFERENCE]
4. Secure: force HTTPS, verify SSL auto-renewal (certbot cron on VPS). [DOC]
5. DNS cutover: set zone records, account for 24–48h propagation before switching traffic. [DOC]

Quality Criteria

• Tier matches workload (no daemons on shared hosting). [INFERENCE]
• Node apps run under a process manager (PM2) with restart-on-boot. [DOC]
• DB user least-privilege; connections pooled/closed within caps. [DOC]
• HTTPS forced; certificate renewal automated and verified. [DOC]
• Claims evidence-tagged. [EXPLICIT]

Anti-Patterns

• Long-running Node daemon on a shared plan (killed/limited). [INFERENCE]
• Opening unbounded DB connections against a low shared cap. [DOC]
• Manual SSL renewal with no cron (expiry outage). [INFERENCE]

Contract

• Aceptación: tier correcto; deploy reproducible (Git/PM2); DB least-priv dentro de caps; HTTPS con renovación automática; DNS con propagación contemplada. [EXPLICIT]
• Límites: hosting tradicional shared/VPS; no serverless/edge ni superficies Firebase. [EXPLICIT]
• Casos borde: carga necesita escalar/serverless → migrar a vercel-platform/firebase-platform. [INFERENCE]
• Supuestos: cuenta Hostinger con acceso hPanel/SSH; credenciales provistas por el usuario. [SUPUESTO]
• Trade-off: costo mínimo y control total en VPS a cambio de ops manual (sin autoscale, parches propios). [EXPLICIT]

Related Skills

• firebase-platform, vercel-platform — sibling target platforms (Platform Lens). [EXPLICIT]
• web-infra-foundation — provider-agnostic DNS/SSL/CDN/backup patterns. [EXPLICIT]
• cicd-release-engineering — deploy automation and rollback. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.