Runtime and processes
Check a webhook receiver that needs stable HTTPS, low-latency acknowledgement, queueing or retry protection, signature validation, logs, and safe handling of burst traffic.
Webhook service VPS
Run a webhook receiver with a public HTTPS endpoint. Plan request validation, retries, logs and any queued work.
Hosting options
Self-managed virtual servers with administrator access, NVMe disks, shared vCPU, dedicated IPv4 and IPv6. RAM uses ballooning. Backups are sold separately.
See VPS hosting →02Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
Check a webhook receiver that needs stable HTTPS, low-latency acknowledgement, queueing or retry protection, signature validation, logs, and safe handling of burst traffic.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.
Field guide
A webhook receiver has one job at request time: verify the sender, record the event, and return a success response quickly, well inside the sender's timeout. Senders such as payment processors retry on slow or failed responses and may disable endpoints that keep failing, so heavy processing belongs in a queue behind the receiver, not in the request path.
Signature verification uses the raw request body and the sender's signing secret, and it must run before any parsing that could alter the body. Store every received event with its headers and payload before processing, so a handler bug can be fixed and the stored copy replayed; you never depend on the sender resending it.
Verify the HMAC or signature against the exact bytes received, before JSON parsing. Frameworks that parse and re-serialize the body change the bytes and break verification.
Key processed events by the sender's event ID and skip ones already handled. Retries and network duplicates are normal, and senders expect receivers to tolerate them.
Measure the receiver's response time under load and keep it a small fraction of the sender's timeout. Work that takes seconds belongs in the queue consumer.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.