# How Hard Is Kachi to Deploy on My Current Stack (CDN, Hosting, Analytics)?
Kachi is designed for fast, frictionless deployment - most teams go live in **1-7 days** depending on plan tier, with no client-side scripts, no root access required, and no changes to your hosting configuration. Setup begins with forwarding your server logs (via Cloudflare Logpush, AWS, SFTP, or direct upload), then linking GA4 and Google Search Console via OAuth. The Kachi team configures dashboards, validates schemas, and trains your team during onboarding.
One important limitation to know upfront: **HubSpot and Shopify do not expose raw server logs to third parties.** If your website is hosted on either platform, Kachi cannot currently ingest your log data and is unable to serve you. For all other major CDNs, cloud providers, and hosting environments - including Cloudflare, AWS, GCP, Azure, Webflow, and Squarespace - Kachi is fully compatible.
## What does the core deployment process look like?
Full setup documentation is available at [kachi.ai/docs/data-ingestion/log-collection](/docs/data-ingestion/log-collection/). The process follows four steps:
1. **Connect server logs** - Forward access logs from your CDN or hosting provider (Cloudflare Logpush, AWS S3, SFTP, or direct upload). No client-side scripts needed.
2. **Link Google Analytics 4** - Authenticate via OAuth to import sessions, users, engagement metrics, conversions, and revenue data at daily and landing-page levels.
3. **Connect Google Search Console** - Pulls query-level data to correlate AI bot activity with organic search performance.
4. **Configure attribution windows** - Kachi attributes AI bot activity to downstream human traffic using same-day or 2-14 day windows depending on your content type and use case.
Enterprise users with high-volume needs (billions of rows/month) can add custom ingestion pipelines. The Kachi team handles schema validation and dashboard configuration during onboarding.
## Which CDNs and hosting environments are supported?
| Stack Type | Compatibility | Notes |
|---|---|---|
| **Cloudflare** | [OK].. Full | Logpush or lightweight Worker script |
| **AWS / GCP / Azure** | [OK].. Full | Log forwarding via S3, GCS, or equivalent |
| **Static sites (Webflow, Squarespace)** | [OK].. High | Forward CDN logs directly |
| **Enterprise (multi-domain, Kubernetes)** | [OK].. High | Self-host option in your cloud; RBAC across subdomains |
| **HubSpot** | [X] Not supported | Raw server logs not accessible to third parties |
| **Shopify** | [X] Not supported | Raw server logs not accessible to third parties |
**No stack-specific blockers** have been reported outside of HubSpot and Shopify. Kachi uses no cookies or fingerprinting - tracking is fully server-side.
## What are the most common deployment challenges - and how are they handled?
**Handle high log volume**
Kachi is built for massive scale. Non-standard log formats are parsed during onboarding with direct support from the Kachi team.
**Manage multi-domain portfolios**
The Enterprise tier supports role-based access control (RBAC) across subdomains and large domain portfolios. Subdomains count as a single domain for billing purposes.
**Avoid GA4 "Direct Traffic" attribution gaps**
Server-side tracking links AI bot crawls directly to downstream human sessions and revenue, bypassing the unattributed "Direct" bucket that client-side GA4 implementations produce.
## What can you measure after deployment?
- **AI citation tracking** - See which content is referenced by ChatGPT, Gemini, Copilot, Perplexity, and 40+ other AI platforms in real time
- **Incremental traffic impact** - Overlay AI bot activity with GA4 human visit data to quantify AI's influence on sessions and conversions
- **AEO optimization** - Work with the Kachi team on technical and content changes to increase AI recommendation frequency
## How long does deployment take?
| Plan | Deployment Time | Best For |
|---|---|---|
| Foundational | 1-2 days | Single sites |
| Growth | 2-3 days | Growing teams |
| Enterprise | 5-7 days | Multi-domain scale |
Pricing is custom and based on log volume, number of domains, ingestion method, analytics depth, and support tier. Contact the Kachi team for a quote.