KaixuPush is a managed Netlify deploy proxy built into the Kaixu Gateway. Push any file set to a Netlify site through a metered pipeline — with per-customer tokens, spend caps, chunked uploads, async completion, and a complete deploy history.
Kaixu API key required. Get yours →
When you manage Netlify sites for multiple clients, token management, deploy tracking, rate limiting, and billing become a full-time side project.
Every client has their own Netlify token. Storing them securely, rotating them, and revoking access without service interruption has no standard solution — until now.
How many deploys did a client trigger this month? How many bytes were uploaded? What did that cost? Without a proxy layer, these answers require manual aggregation.
Netlify enforces deploy rate limits per token. When multiple clients share infrastructure, a burst from one can throttle others — unless you have per-customer rate pacing built in.
KaixuPush breaks deployment into discrete API steps — each audited, rate-paced, and capped independently. No opaque magic, no silent failures.
{ wait: true } for synchronous completion with a 120s timeout. Records billing event on success.ready and retrieve the live URL.Build a JSON map of { "path": "sha1hex" } for every file you want in the deploy. POST it to push-init with your Kaixu key. The gateway checks your caps, validates your project, creates a Netlify digest deploy, and returns the list of required file SHAs — only the files that actually changed.
For each SHA in the required list, PUT the file binary to push-upload with the matching X-Content-Sha1 header. For files over the inline upload threshold, use push-upload-chunk to stream in parts — the gateway assembles and commits them in a background job. Already-known SHAs are skipped automatically.
Once all required files are uploaded, POST push-complete. The default path queues background finalization and returns 202 immediately — no waiting for Netlify's deploy pipeline. For synchronous finalization, pass { wait: true }; the gateway will poll Netlify for up to 120 seconds before returning the result.
GET push-status with your pushId at any interval. The response includes the gateway's internal record plus a live Netlify deploy state refresh. When state is ready, the ssl_url field contains the final, SSL-provisioned deploy URL. Errors surface with the Netlify error_message for immediate diagnosis.
Every successful deploy writes a push_usage_event to the Kaixu Neon DB — deploy count, byte count, pricing version, and cost in cents. Monthly invoices aggregate automatically. Deploy history is queryable from the Gateway admin dashboard for any customer, any month.
Each customer registers their own Netlify API token — stored encrypted in Neon. Deploys run under the customer's own Netlify account, within their own plan limits. No shared token risk.
Set monthly deploy limits and byte caps per customer. Rate pacing enforces a maximum of 3 deploys per minute and 100 per day by default — configurable per deployment. Cap-exceeded requests return 402 immediately with remaining budget details.
The SHA1-based digest manifest means only files that have actually changed are uploaded to Netlify. Unchanged files are skipped automatically. A 500-file site with 10 changed files sends 10 PUT requests, not 500.
Background jobs handle deploy finalization. If a job fails (Netlify transient error, rate limit), the push-job-retry scheduler retries it every 5 minutes with exponential backoff — up to 10 attempts, configurable.
Files too large for a single serverless request are split and streamed in binary chunks. Each chunk is stored with 48h retention, assembled, and committed server-side. No client-side multi-part split logic required.
Every push-init, push-upload, and push-complete is logged to the gateway audit table with customer ID, key ID, project ID, byte count, and timestamp. Full deploy history queryable from the admin dashboard.
KaixuPush is the deployment layer. Pair it with the tools that generate the content and the UI that monitors the result.
Use skAIxU IDE Pro to AI-generate the HTML, CSS, and JS for any site or page. When the output is ready, pipe the file map directly to a KaixuPush init call.
Init → upload changed files → complete → poll status. Your site goes live on Netlify under the customer's own account — tracked, metered, and invoiced through the gateway.
The Kaixu Gateway admin dashboard shows deploy history, chunk jobs, byte totals, and invoices per customer per month — no separate reporting tool needed.
Per-customer tokens. Spend caps. Digest-only uploads. Async completion. Full billing history. KaixuPush is the deploy proxy you'd have to build yourself — already built.
Kaixu Gateway account required. Talk to SOL →