Paused public site
The homepage and pricing page are both paused, so the product’s live functionality is not visible from the provided sources.
Draft Horse AI’s public site is paused, with only brand, domain, and a 503 deployment state visible.
Draft Horse AI is a website whose public homepage and pricing page are currently unavailable because the deployment is paused. The accessible source content does not expose the product’s core feature set, target user, or working product experience.
Based on the available pages, the only confirmed information is that the site is hosted on Vercel and that both the home and pricing routes return a 503 deployment-paused message. Any deeper description of the product would be speculative from the provided evidence.
The homepage and pricing page are both paused, so the product’s live functionality is not visible from the provided sources.
The deployment error page confirms the site is served through Vercel and that the owner has paused the deployment.
The visible pages include a pricing route, which suggests the product may have a commercial plan structure, but no plan details are exposed.
The error pages identify the deployment state clearly, which helps distinguish a temporary outage from a client-side issue.
A visitor checking the homepage will learn that the service is temporarily unavailable and that the issue is on the deployment side rather than their own connection.
Someone evaluating the product can verify the brand name and the existence of a pricing route, even though pricing content is not currently published.
A site owner or operator can use the error state to confirm the deployment is paused and then resume the service when ready.
The available source only shows that the site is paused with a 503 deployment status, so the product’s setup, workflow, and support details are not accessible from the pages provided.
From the accessible pages, no product-specific pricing details are visible. The pricing page is also paused, so pricing structure cannot be confirmed.
No integrations are documented in the accessible source pages, so supported tools and connections cannot be confirmed here.