llms.txt
Compare with other sites' llms.txt files →# Fusionaly
> Self-hosted web analytics in one SQLite file. Your visitors' data stays on your server, not a third party's. Free and open source (MIT); you pay only for your server.
Fusionaly is one free, open-source product. There are no tiers, no license to buy, and no paid plan. A paid Pro edition existed before; it is gone, and its features (the activity feed and Ask AI) are now in the free product. Support comes from the community through GitHub issues and discussions. There is no SLA.
It is built by Carlos Castellanos (@karloscodes), a solo developer, as a calm side project. It is not a VC-funded startup. His view: once your visitors' data sits on someone else's server, they set the terms. They can raise the price, change the rules, get breached, or shut down.
**What is included:**
- Dashboard: visitors, page views, referrers, UTMs, top pages, countries, devices
- Unlimited events and unlimited websites
- Visitor flows, goal conversions, annotations, and shareable public dashboards
- Automatic tracking of page views, SPA navigation, and button clicks
- One attribute, `data-fusionaly-event-name`, tracks clicks on links, form submits, and sections that scroll into view
- Revenue tracking, a JavaScript API for custom events, and subdomain tracking
- Activity feed: a daily list of what changed, such as traffic spikes and drops, new referrers, goal spikes, trending pages, and milestones. It compares yesterday with the same weekday over the past 8 weeks.
- MCP server at `/mcp`: Claude Code, Codex, Cursor, Gemini CLI, or any MCP client can ask questions about your analytics. Optional. Four read-only tools, an agent key you create, and your database stays on your server. Fusionaly itself never calls an AI provider.
- SQL API at `/z/api/v1/sql` for scripts and clients without MCP, with the same read-only agent key
- Five themes: Light, Dark, Phosphor, Catppuccin, and Gruvbox
- Bot filtering, rate limiting, and an origin check on every event
**Privacy:** No cookies, and nothing is stored on the visitor's device. Each visitor gets an ID hashed with a salt that changes every day at midnight UTC, so nobody is followed from one day to the next. The raw IP address is not stored. The SDK respects Do Not Track by default. Visitors can see what Fusionaly knows about them at `/x/api/v1/me`.
**Install:** Run `curl -fsSL https://fusionaly.com/install | sudo bash -s data.example.com` on a fresh Ubuntu or Debian server as root. It installs Chasen (and Docker when needed), sets up HTTPS, nightly updates, and live database backups to S3 or local storage. You can also run the Docker image `karloscodes/fusionaly` (AMD64 and ARM64) on two registries: Docker Hub and `ghcr.io/karloscodes/fusionaly`. Minimum server: 1 vCPU, 512 MB RAM, 10 GB SSD. It runs on a $5 VPS or a Raspberry Pi.
Then add the tracking script to your site:
```html
<script defer src="https://your-domain.com/y/api/v1/sdk.js"></script>
```
The script loads from your own domain, so ad blockers see your site, not a tracker. Do not host Fusionaly on an `analytics.*` subdomain: ad blocker lists block hostnames like that. Use a neutral one such as `data.example.com`.
**Why one SQLite file:** A backup is a file copy. Moving servers is copying one file. Any SQLite tool can query your data with plain SQL. There is no database server to run. Plausible self-hosted needs PostgreSQL and ClickHouse in several containers. Matomo needs a MySQL server. Fusionaly is one container and one file.
**Architecture:** The browser SDK sends events every 200 ms (up to 10 per batch), retries 3 times with backoff, and keeps up to 100 events in localStorage when offline. The server writes events to a durable queue table. A background job runs every 60 seconds and moves them in batches of 100 into hourly aggregate tables. Dashboards can lag by about a minute during a spike, but events are not dropped. When saturated, the server returns `503` with `Retry-After`, and database writes retry up to 10 times on `SQLITE_BUSY`. SQLite runs in WAL mode, so reads do not wait for writes. A modest server handles about 400 requests per second. Most dashboard queries take under 10 ms. Each event uses about 240 bytes, so 100K daily visits is about 72 MB per day, or 26 GB per year.
**Who it is for:** Indie hackers, small SaaS products, personal projects, agencies with client sites, and anyone who wants to own their analytics data. It is not built for enterprise scale across tens of millions of daily users.
**Compared to alternatives:**
- Google Analytics: Fusionaly keeps data on your server, has no ads, and gives you direct SQL access to your data.
- Plausible Cloud: No subscription fee, and you can query the database directly.
- Plausible self-hosted: One SQLite file and one container, not PostgreSQL plus ClickHouse.
- Matomo: SQLite, not MySQL. No database server to manage.
## Docs
- [Documentation home](https://fusionaly.com/docs/): Overview of Fusionaly and links to every guide
- [What's Included](https://fusionaly.com/docs/editions/): Every feature of the one free product
- [Installation](https://fusionaly.com/docs/installation/): Install on your own server with Chasen, or run the Docker image yourself
- [Manage](https://fusionaly.com/docs/manage/): Update, back up, and run your server, and manage your websites and accounts
- [Getting Started](https://fusionaly.com/docs/getting-started/): Add the tracking script and verify that events arrive
- [SDK Configuration](https://fusionaly.com/docs/configuration/): SDK options such as Do Not Track, auto-tracking, and the host setting
- [Local Demo](https://fusionaly.com/docs/demo/): Run Fusionaly on your machine with Docker
## Tracking
- [Tracking](https://fusionaly.com/docs/automated-tracking/): Automatic page views and button clicks, and the `data-fusionaly-event-name` attribute
- [Section Tracking](https://fusionaly.com/docs/section-tracking/): Fire an event when 50% of an element is visible
- [Revenue Tracking](https://fusionaly.com/docs/revenue-tracking/): Track purchases with price, quantity, and currency
- [JavaScript API](https://fusionaly.com/docs/custom-events/): Send custom events that HTML attributes cannot express
- [Subdomain Tracking](https://fusionaly.com/docs/subdomain-tracking/): Track several subdomains as one website
- [Generic Integration](https://fusionaly.com/docs/integrations/generic/): Add Fusionaly to any website or web application
## Framework guides
- [Next.js](https://fusionaly.com/docs/integrations/nextjs/): A Script tag in app/layout.tsx; client-side page changes are counted
- [React](https://fusionaly.com/docs/integrations/react/): A script tag in index.html (Vite); React Router page changes are counted
- [Astro](https://fusionaly.com/docs/integrations/astro/): An is:inline script tag in the layout; works with view transitions
- [Nuxt](https://fusionaly.com/docs/integrations/nuxt/): app.head.script in nuxt.config.ts; $production for production only
- [SvelteKit](https://fusionaly.com/docs/integrations/sveltekit/): A script tag in src/app.html
- [WordPress](https://fusionaly.com/docs/integrations/wordpress/): A must-use plugin in wp-content/mu-plugins that skips logged-in users
- [Shopify](https://fusionaly.com/docs/integrations/shopify/): A script tag in layout/theme.liquid; the checkout is not tracked
- [Webflow](https://fusionaly.com/docs/integrations/webflow/): Head code in Site settings, and custom attributes for events
- [Ghost](https://fusionaly.com/docs/integrations/ghost/): Site header code injection
- [Hugo](https://fusionaly.com/docs/integrations/hugo/): The head partial, inside hugo.IsProduction
## AI clients
- [Agents](https://fusionaly.com/agents/): The MCP server, the plugin, the skills, and the SQL API
- [AI Clients (MCP)](https://fusionaly.com/docs/agent-api/): Connect Claude Code, Codex, Cursor, or Gemini CLI, and the SQL API reference
## Administration
- [Manage](https://fusionaly.com/docs/manage/): Update, back up, and run your server from your computer or on the server
- [Move to Chasen](https://fusionaly.com/docs/move-to-chasen/): Move an older server to Chasen for better backups and commands
## Technical
- [How It Works](https://fusionaly.com/docs/how-it-works/): The SQLite ingestion pipeline, retries, aggregation, and storage estimates
- [Data Integrity](https://fusionaly.com/docs/data-integrity/): Origin checks, bot filtering, and rate limiting
- [Visitor Transparency](https://fusionaly.com/docs/visitor-transparency/): The `/x/api/v1/me` endpoint that shows visitors their own data
## Optional
- [Why Fusionaly](https://fusionaly.com/why-fusionaly/): Why Fusionaly runs on one SQLite file on your own server
- [Live demo dashboard](https://t.fusionaly.com/share/QdREgX5mZu5y): The real, public dashboard for fusionaly.com
- [What Fusionaly knows about you](https://fusionaly.com/visitor-transparency/): Your own visitor data on fusionaly.com, fetched live
- [Source code on GitHub](https://github.com/karloscodes/fusionaly-oss): The MIT-licensed application, installer, and plugin
- [Scroll Signals (deprecated)](https://fusionaly.com/docs/scroll-signals/): Legacy scroll tracking attributes; use `data-fusionaly-event-name` instead
- [Privacy Policy](https://fusionaly.com/privacy-policy/): The privacy policy for fusionaly.com
- [Stats](https://fusionaly.com/stats/): downloads from Docker Hub and ghcr.io, GitHub stars, versions, and how we count