Hpanel Integration?

[kenlyle2]

Hpanel is a real relief to me after dealing with cPanel. The CDN is integrated, not tacked on, and WordPress updates have smarter options. Their AI actually fixed some obscure issues, which it reported as permissions issues.

Can we get hpanel (Hostinger) integration?

[superdav42]

Thanks for the suggestion. hPanel/Hostinger integration is a meaningful feature request — adding to the maintainer review queue for scoping before any implementation work begins.

If you have details on which specific hPanel APIs or features would be most valuable for integration (CDN config, WP update controls, permissions sync, etc.), adding that context here would help prioritise.

---

aidevops.sh v3.8.42 plugin for OpenCode v1.4.6 with claude-sonnet-4-6 spent 2m and 6,307 tokens on this as a headless worker. Overall, 24m since this issue was created.

[kenlyle2]

Thanks very much, @superdav42

I think you know best. From what you named, I think that their CDN is automatic, or a toggle.
I think that creation of the wildcard subdomain CNAME would be valuable.
WP Update Controls are good, they allow for Core, Themes, and Plugins either Security Only, All, or None.

Overall, instead of trying to create a mirror UI to try to make it "zipless", let hPanel continue to evolve in parallel - like you did with my Idiot Resistance request - If you show onscreen AND via email - Do these things - and also leverage Hostinger's Kodee AI - it's super easy to figure out the steps, and sometimes Kodee will even execute them for you- I believe "he" created my wildcard CNAME for me. I use the term "loosely coupled"- so that you are not breaking your head tracking hPanel API changes.

[superdav42]

Review: Approved

Issue Validation

Check	Status	Notes
Reproducible	N/A	Feature request, not a bug
Not duplicate	Yes	No hPanel/Hostinger issues in recent closed list; existing integrations cover cPanel, Cloudflare, etc.
Actual bug	N/A	Enhancement — new host provider integration
In scope	Yes	Project has inc/integrations/ with existing host provider integrations (cPanel, Cloudflare); this is the intended extension point

Root Cause: Not a bug. This is a well-articulated feature request from an active user (kenlyle2) who has prior engagement with the project (referenced their earlier "Idiot Resistance" request, visible as merged PR #878). Hostinger is a major WordPress host, and hPanel is their proprietary control panel. The user's second comment adds meaningful scoping: they explicitly advocate a loosely-coupled approach — guided instructions + leveraging Hostinger's Kodee AI — rather than deep API mirroring, which reduces implementation burden and API-breakage risk.

Scope & Recommendation

• Scope creep: Low — user self-scoped to a few concrete features (wildcard CNAME, WP update controls) and explicitly discouraged building a mirror UI.
• Complexity tier: tier:thinking — this is a research/architecture task. Hostinger's hPanel API is not publicly documented in the same way cPanel's is. Before any implementation, someone needs to investigate what APIs exist (if any), what can be automated vs. guided, and whether to model this on the existing cPanel integration pattern or take the lighter "guided setup" approach the user suggested.
• Decision: APPROVE
• Recommended labels: enhancement, needs-maintainer-review, integration
• Implementation guidance:
  • Phase 0 (research): Investigate Hostinger/hPanel API availability. Check if there's a public REST API, reseller API, or if automation is limited to Kodee AI chat commands. The existing cPanel integration at inc/integrations/ is the reference pattern — determine if hPanel offers equivalent programmatic access or if the "loosely coupled" guided-instruction model is the only viable path.
  • Scope the MVP narrowly: Based on user input, the highest-value features are (1) wildcard subdomain CNAME creation guidance/automation and (2) WordPress update policy configuration (core/themes/plugins × security-only/all/none). CDN is reportedly automatic on Hostinger, so it may need no integration at all.
  • Keep this as a parent/tracking issue. Once research completes, decompose into child tasks for specific integration points. Do not attempt implementation until the API surface is understood — the user themselves warned against tight coupling to an evolving panel.