Marketing automation on Vultr
Campaigns, contact segmentation and marketing workflows.
1 documented option on Vultr. 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 |
|---|---|---|---|---|---|
| Typebot | Vultr, Hostinger, Railway | Customer-operated Servers / containers | Source Available FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion. | Application platform deployment; 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 evidenceCurrent FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
Cloud evidence reviewed 2026-11-19 |
Deployment evidence and category fit
Typebot
Self-hosted visual conversation and form builder.
Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
- Vultr Docs ↗
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Deployment and procurement checks
- VPC provisioning
- Vultr documents isolated IPv4 VPC networks with console, API, CLI and Terraform provisioning. Configure the selected location, address ranges and routes; private application access is separate from public ingress. 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: Vultr account and compute instances. Access: Cloud account access and server SSH keys. Network: Instance networks and firewall rules.
Provider documentation ↗ · Guidance reviewed 2026-11-12. 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