Cloud vs. Self-Hosted

The cloud version is a Managed-Service and, like the self-hosted version, is based on the Delivery Tracker Core code, which is publicly available on GitHub. In addition to the publicly available code, there is a variety of code and systems in place to ensure the stability and additional features of the cloud version of the service.

Here are the main differences users might notice

	Cloud	Self-Hosted	Description
Ease of management	✅ ✅	❌	Cloud: Managed-service, so you don't have to worry about setting up or maintaining complex infrastructure. Self-Hosted: You have to manage scraper code changes, infrastructure management, failure response, and more. This can require additional technical expertise and resources.
Service reliability	✅ ✅	❓	Cloud: We maintain the reliability of our services through a variety of internal systems. Users can use the service without much difficulty.
Query.track API	✅ ✅	✅ ✅	Cloud: You can easily use the Tracking API through API calls. There are a number of technical measures in place to ensure stability. Self-Hosted: You can leverage Docker within the scope of permitted licenses to configure basic APIs like Query.track yourself. Additional development and technical expertise may be required for stability.
Tracking Webhook API	✅ ✅	❌	Cloud: Easily detect changes in the status of a waybill through the Webhook API.
Extending the Tracking API	✅ ✅	❌	Cloud: We are providing additional features such as searchText in Query.carriers.
Quotas	Quotas	❓	Cloud: Project-specific [Quotas policy] (/docs/quotas) applies. Self-Hosted: Depends on your development or infrastructure. You should also consider quotas on the carrier server side.
Customizing	🔍 â	✅ ✅	Self-hosting: You can modify the published code to modify and further develop the API to operate in your context.
User experience	-.	-.	Cloud: Generally offers a more user-friendly interface and features. Self-Hosted: Customizable based on your investment of development resources.