Workflow automation on Hostinger
Business automation, integrations, scripts and API workflows.
2 documented options on Hostinger. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Corteza | Hostinger | Customer-operated Servers / containers | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. | Docker / Compose | Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.Scope and evidenceCRM workflows require configuration; a general platform is not a packaged vertical business solution.
Cloud evidence reviewed 2026-11-19 |
| DocuSeal Self-Hosted | AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock, Azure, Google Cloud, Railway, Heroku, Render | Customer-operated Servers / containers | Open Source / Open Core AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms. | Vendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM. | Customer manages administrator access, signing workflows, HTTPS, secrets, database networking, mail, durable attachment storage, database/file/key recovery and image upgrades. Platform providers operate the underlying managed services. For 3.3.8 security remediation, restart every Ruby web and background process after deployment.Scope and evidenceReviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.
Cloud evidence reviewed 2026-11-13 |
Deployment evidence and category fit
Corteza
Low-code platform for business records, workflows and configurable CRM applications.
CRM workflows require configuration; a general platform is not a packaged vertical business solution.
- Hostinger ↗
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Corteza server, web applications, database and object or file storage. CRM workflows require configuration; a general platform is not a packaged vertical business solution.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
DocuSeal Self-Hosted
Automates document form filling, signature collection and completion workflows through a self-hosted application, API and webhooks. This does not establish full contract lifecycle management or regulated-record compliance.
Reviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.
- Hostinger customer VPS Cloudron template ↗
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
Cloud evidence reviewed 2026-11-13. Full listing and qualifications
Deployment and procurement checks
- VPS hardening
- The provider recommends SSH hardening, firewall configuration and patching for VPS hosts. A preinstalled application template does not transfer these operating responsibilities away from the customer. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: Hostinger account and VPS. Access: Cloud account access, server root/SSH access and application administrators. Network: Customer server networking, DNS and firewall rules.
Provider documentation ↗ · Guidance reviewed 2026-11-13. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings