Integrations
What a PolyDraft site actually connects to
A PolyDraft site connects to things you control: your own cloud account, your domain, your analytics snippet, your anti-spam keys, and a REST content API for publishing from outside tools. Everything else on this page is deployment architecture, not a partner integration.
On this page
Last updated
01 — Yours
Connections you control
These are the real connection points: accounts and keys that belong to you, wired into the site through settings you can change or remove. Nothing here routes through us as a middleman.
Your own cloud account
Deployment targets a Cloudflare account you own. You supply the credentials, the site runs under your billing, and you can revoke access at any time. Updates never reset live content, and cancelling a subscription does not take the site down.
Deploy, with your own account credentials
Your own domain
The published site serves from your domain, not a platform subdomain you would have to migrate off later. Canonical URLs, the sitemap and structured data are all generated against it.
Site settings
Analytics and third-party scripts
A dedicated settings field injects your own snippet into every page — an analytics tag, a chat widget, whatever you already use. It is your script under your account; we neither proxy it nor read it. Every call-to-action, form submit and tool interaction already carries a stable data-analytics attribute for your triggers to bind to.
Admin → Settings → script injection
Anti-spam keys you own
Contact forms support Cloudflare Turnstile using your keys. The widget renders nothing until you add a site key, and the server only verifies submissions once you have also added the secret key. No keys, no third party involved.
Admin → Settings
REST content API
Blog posts can be created and updated over HTTP with a bearer token you generate, so an external writing tool or an AI agent can publish straight into the site. The admin panel documents every endpoint against your live schema, including any custom collection.
Admin → API docs
Google sign-in
Access to the builder itself uses a Google account. We never hold a password of yours.
Builder sign-in
02 — Architecture
Where your site runs
The items below are not integrations. You do not connect them, and there is nothing to configure. They are what a finished site is made of and where it runs once deployed into your own cloud account. We list them because a buyer evaluating ownership deserves to know what they are taking custody of — not because a technology stack becomes a partner logo when a marketing page needs one.
Edge runtime
Pages are rendered and served from a global edge network, which is what keeps load times consistent for visitors far from any single region.
SQL database
Blog posts, categories, inquiries, images metadata, showcase entries and site configuration live in a SQL database provisioned inside your own account. Schema changes ship as additive migrations, so a redeploy never wipes what is already there.
Object storage for media
Uploaded and generated images are stored as objects and served through the site’s own media route. Replacing an image in the library swaps the file without changing the URL, so pages do not break.
Static output with server rendering
The site is a real server-rendered site, not a client-side shell: crawlers and AI assistants receive complete HTML on the first request rather than an empty page waiting on JavaScript.
On the Agency plan the whole thing exports as source code, which is the point: what you receive is a real codebase in infrastructure you own, not a tenancy. The access and approval side of this is on security, and the commercial side on the agencies page.
Leaving
Export and transfer
The honest test of an integrations page is what happens when you stop paying. Because the site is deployed into your own cloud account under your own domain, ending a subscription does not take it down — there is no tenancy to be evicted from, and nothing to migrate off.
- Source-code export on the Agency plan: the generated site leaves as a standard Node-based web project with its own build script and dependency manifest, not an archive that only opens in one product.
- Project transfer, including the deploy credentials, so an agency can hand a finished site to the client who will own it.
- Content stays yours: redeploying an existing site does not reset the pages, posts and images already published from the admin panel.
The plan-by-plan detail of which of these is included where is on pricing, and the handover workflow on the agencies page.
Unsupported claims
What we do not integrate with
If you are here to check whether we plug into a specific tool, the answer is almost certainly no, and it is more useful to say so than to leave you inferring it from a logo grid.
- We have no integration with automation platforms such as Zapier, and no app in any workflow marketplace.
- We have no chat or messaging integration — no Slack app, no Teams app, no Discord bot.
- We have no CRM or marketing-automation integration, including HubSpot, Salesforce and Mailchimp.
- We have no e-commerce or payment integration you can add to a generated site.
- We do not import from, export to, or sync with other site builders and CMS platforms, including WordPress, Webflow, Wix and Squarespace.
- We publish no plugin marketplace and no public app directory.
The escape hatch is the content API and the script-injection field above: between them, most tools can be pointed at a site without us building anything. If something you need is genuinely blocked, write to support@polydraft.ai and say what it is.