Describe the site. Generate the build. Push to production. statikAI is the AI-powered static site builder and deploy pipeline — turning a plain-language brief into a production-ready static site, pushed to Netlify via the KaixuPush deploy proxy in a single tracked, metered deploy chain.
Every new static site starts with the same overhead: initialise a project, configure a build, connect a repo, link to Netlify, set up environment variables, push the first empty commit. By the time the actual content begins, the momentum is already gone. Simple sites deserve a simple pipeline — one that starts with the brief, not the boilerplate.
Agencies and operators build the same site archetypes repeatedly: law firm landing page, local service site, product microsite, campaign page. Each time, the code is written from scratch, the deploy is configured manually, and the handoff is documented after the fact. Without a generate-and-push pipeline, every project starts at zero.
When sites are deployed manually — drag-and-drop, CLI pushes, direct Netlify dashboard deploys — there's no tracking layer, no deploy history, no metered billing record. Agencies and platform operators who push on behalf of clients have no structured way to log, invoice, or audit the deployment activity they generate.
Describe the site in plain language — the type, the client, the industry, the content sections, the tone. statikAI generates a production-quality static HTML/CSS build from the brief, structured for immediate deployment. No scaffolding, no template selection, no manual component assembly. The brief becomes the build.
Every site pushed through statikAI routes through the KaixuPush deploy pipeline — a structured Netlify deployment proxy that handles chunked file uploads, digest verification, deploy state polling, and URL resolution. The push is not a drag-and-drop — it's a full API-driven deploy chain with status tracking from init to ready.
Every deploy is logged: push ID, project ID, branch, deploy state, file count, bytes uploaded, and timestamp. Deploy history is queryable by project and month. Usage events — deploys ready, bytes uploaded — are metered in real time. Nothing falls through the cracks of an unseen Netlify dashboard action.
For platform operators and agencies managing deploys on behalf of clients, statikAI's KaixuPush backend generates per-customer, per-month invoices from actual usage data — deploys ready, bytes uploaded, pricing version. The invoice is derived from the metered pipeline, not manually calculated.
Every push is authenticated with a Kaixu Bearer key scoped to a customer identity. Project registration (project ID + Netlify Site ID) is required before the first deploy. The authentication layer means every push is tied to an owner, every deploy is attributable, and rogue pushes are structurally impossible.
Beyond direct file pushes, statikAI supports GitHub repository pushes through the KaixuPush GitHub integration — push a repository's content to a Netlify site directly from the pipeline, with chunked upload support for large repos. Branch targeting, commit messages, and job tracking are all included.
Before the first push, register the project in statikAI — give it a project ID, a human-readable name, and the Netlify Site ID it will deploy to. The project registration binds future deploys to a specific Netlify site, customer account, and billing record. Registration is a one-time step per project. All subsequent pushes reference the project ID.
Describe the site in the statikAI generator — business type, content sections, tone, colour direction, target audience. The AI build produces a complete static site: structured HTML, embedded CSS, optimised for immediate Netlify deployment. No template selection, no drag-and-drop builders, no manual component assembly. Plain language in, production-ready files out.
The generated build is pushed to the KaixuPush pipeline with the project ID, branch target, and deploy title. The push-init function creates a Netlify digest deploy — all files are SHA-256 hashed, the digest manifest is submitted to Netlify's API, and required file digests are returned for upload. The deploy is registered in the push log immediately.
Files required by Netlify (those not already in their CDN cache from previous deploys) are uploaded through the push-upload pipeline — chunked for large builds, streamed for standard builds. Each upload is logged as a usage event. When all required files are uploaded, push-complete finalises the deploy and polls for the ready state — returning the live SSL URL when confirmed.
The deploy is logged in the push history: push ID, state, bytes uploaded, file counts, and timestamp. Usage events accumulate in the metering layer throughout the month. At any point, generate a per-customer invoice for the month — structured from actual metered data, not estimated usage. Repeat for the next project with a new brief and a single push-init call.
Agencies building local business sites, campaign pages, and client microsites at volume need a pipeline that eliminates per-project scaffolding overhead. statikAI generates the build from the creative brief and pushes to the client's Netlify site through a tracked, invoiceable deploy chain — without a git repo, CI configuration, or Netlify dashboard for every project.
Developers building platforms that need to publish static sites on behalf of their users — white-label site builders, local marketing platforms, client portal generators — can use statikAI's KaixuPush API as the deploy layer. Every user-initiated site publish routes through a tracked, metered deploy pipeline with per-customer billing built in.
Teams moving from brief to deployed product in hours, not days, need a deployment path that doesn't require infrastructure setup before the first line of content. statikAI gives MVP teams a working URL before the CI pipeline is even configured — and a tracked deploy record for every iteration along the way.
Solo operators managing multiple client sites need a deploy chain that scales without adding operational complexity. One API key, multiple registered projects, a push-init call for each new deploy, and a monthly invoice per client — statikAI turns a portfolio of site deployments into a structured, billable service without a custom backend.
Operators building sites for local businesses — law firms, contractors, medical providers, retail — want to generate industry-appropriate static sites without rebuilding the same layouts from scratch each time. The AI generation layer produces correctly-structured local business sites from a brief, eliminating the repetitive manual build work.
Development teams integrating static site deployment into larger automation workflows — content pipelines, CMS-triggered deploys, form-to-site generators — can use statikAI's KaixuPush API endpoints as a programmable deploy layer. Authenticated, tracked, and metered deploys from any upstream trigger in the pipeline.
A Phoenix web agency manages 15 active client sites across various industries. Without statikAI: each new client requires a github repo, Netlify site setup, environment configuration, and a first commit before any content begins. With statikAI: register the project once (project ID + Netlify Site ID), generate the build from the intake brief, push via KaixuPush, get the live URL back. Generate a monthly invoice per client from actual deploy usage. The agency's deploy process scales without growing its infrastructure team.
A developer is building a white-label site builder where business owners can publish their own branded sites. The platform needs to push sites to individual Netlify projects on behalf of users — tracked and billed per user. Integrating statikAI's KaixuPush API as the deploy layer means every publish button press routes through an authenticated, metered, invoiceable deploy chain — without the platform developer building a custom Netlify deploy backend from scratch.
A marketing team needs a dedicated landing page for a campaign that goes live in 24 hours. Traditional path: brief the developer, wait for build, wait for review, configure deploy, push, debug DNS. statikAI path: brief the AI generator, review the output, push via KaixuPush, get the live URL in one session. The Netlify site was registered once at the campaign series level. The specific campaign's page is a new push-init call with a new branch or title — tracked separately in the deploy log.
An agency delivers a completed project to a client via a GitHub repository. The client wants the current repository state live on their Netlify site without connecting their own repo to Netlify. The statikAI GitHub push integration pushes the repository content directly to the client's Netlify site through the KaixuPush GitHub pipeline — authenticated with the client's Kaixu key, branch-targeted, chunk-uploaded for large repos, and logged as a tracked deploy event.
| Capability | statikAI | Netlify Drop | Git Deploy | Netlify CLI |
|---|---|---|---|---|
| AI site generation from brief | ✓ Built-in | ✗ No | ✗ No | ✗ No |
| API-driven deploy (no UI required) | ✓ KaixuPush API | ✗ Manual drag-drop | ✓ Git push | ✓ CLI command |
| SHA-256 digest verification per file | ✓ Yes | ✗ No | ✓ Via Netlify | ✓ Via Netlify |
| Per-deploy tracking & history log | ✓ Full log | ✗ Netlify UI only | ⚠ Netlify UI only | ⚠ Netlify UI only |
| Per-customer metered billing | ✓ Built-in | ✗ No | ✗ No | ✗ No |
| Monthly invoice generation | ✓ From usage data | ✗ No | ✗ No | ✗ No |
| GitHub repo push integration | ✓ Yes | ✗ No | ✓ Native | ⚠ Indirect |
| No local environment required | ✓ Full web app | ✓ Browser only | ✗ Git client required | ✗ Node.js required |
push-init — Initiate a deploy, submit file digests, receive required upload list.
push-upload — Upload required files to the open deploy.
push-upload-chunk — Stream large files in chunks to the upload pipeline.
push-complete — Finalise the deploy and poll for the ready state.
push-status — Query the current state of any active deploy.
push-projects — List registered projects for a customer.
push-billing — Query metered usage for a billing period.
push-whoami — Verify API key identity and role before a push session.
gh-push-init + gh-push-upload-chunk — GitHub repo push with chunked upload and background processing.
push-job-retry — Retry a failed deploy job without re-uploading unchanged files.
"A deployment pipeline that lets clients push sites to Netlify through your gateway. Each deploy is tracked, metered, and invoiced — the infrastructure layer that turns Netlify into a multi-tenant deploy service."
— KaixuPush · Deploy Proxy · SOLEnterprises Gateway DocumentationWhen a statikAI deploy goes live, generate a SkyeDocx delivery contract that includes the live URL, deploy ID, and project scope as embedded exhibits. The delivery documentation writes itself from the deploy log — no manual writeup required.
Pull the monthly KaixuPush invoice data directly into SkyeLedger as a revenue entry — deploys delivered, bytes consumed, billing total. The deploy pipeline's metered usage becomes the ledger line item without manual data entry.
Convert a completed statikAI deploy workflow into a SkyeOps runbook — capturing the project ID, generation brief, push sequence, and deploy resolution as a repeatable SOP. The next project of the same type runs from the runbook, not from memory.
Every static site you're still scaffolding manually is time the pipeline should already be handling. statikAI turns a plain-language brief into a tracked, metered, invoiceable Netlify deploy — from first description to live URL in a single session.
AI site generation · KaixuPush deploy · tracked · metered · invoiced