analytics.gitopen.dev

Open Analytics offers two ways to start without paying upfront: a Startup plan that is free for 1 year for up to 100 projects, and a 14-day free trial on paid plans. The Startup plan is described as "free to apply," so access depends on an application rather than automatic signup. If you want to validate realtime analytics on a small number of sites at no cost, the Startup plan is the natural first step; if you need capabilities beyond what it covers, the paid trial lets you test the full product for 14 days.

What each option includes

The page does not publish paid-plan prices, feature tiers, or what happens after the 14-day trial ends. Treat any comparison of free vs. paid functionality as something to confirm on the official site before committing.

Who each option fits

Choose the Startup plan if you are a founder, small team, or agency that wants to run realtime analytics across many small sites — up to 100 projects — and can accept an application step. The 100-project ceiling is unusually generous for a free tier, which makes it practical for portfolios, client work, or side projects.

Choose the 14-day paid trial if you need to evaluate the full feature set before deciding, or your usage would exceed what the Startup plan covers. Fourteen days is enough to run a real traffic cycle and check whether the realtime view, traffic-source tracking, and SEO-related insights match how you work.

What you get regardless of plan

The product centers on realtime activity rather than historical reporting:

• Live visitor tracking — see who is on your site now, which pages they view, where they came from, and how they move through the site, including an interactive visitor map.
• Traffic source and campaign tracking — referrals, campaigns, and organic search performance in one place.
• SEO insights alongside analytics — Domain Authority tracking, Search Console data, and SimilarWeb insights without switching tools.
• Crawl and indexing monitoring — see when search engine bots discover, revisit, or ignore content.
• Public dashboards — share analytics with clients, teammates, or investors without giving them account access; viewers need no login.
• Simple setup — sign in with Google or GitHub, create a project to get a site key, then paste one script tag into your HTML or Next.js layout. Events post to your Open Analytics server and land in your PostgreSQL database.

How to decide

1. Estimate your project count. If you are under 100 projects, the Startup plan covers you for a year at no cost — apply first.
2. Check whether the free plan's feature set is enough. The page does not spell out differences between free and paid features, so verify this on the site if a specific capability is essential.
3. If you need more, start the 14-day trial and test the exact workflows you care about — realtime monitoring, source attribution, SEO data — during the trial window.
4. Confirm pricing before the trial ends. Since paid-plan prices are not published on the page, get current numbers from the site or sales before the 14 days run out.

The main caveat: because the free Startup plan requires an application, it is not an instant, guaranteed free tier. Plan for a short approval step before you can add the script and start collecting data.

Open Analytics (analytics.gitopen.dev) describes itself as "simple, fast, and privacy-friendly" website analytics, and its realtime tracking works by showing visitors while they are still on your site — current pages, traffic sources, and an interactive visitor map — rather than only historical reports. Privacy-friendliness here is a positioning claim from the site itself; the page evidence does not detail specific compliance certifications, data retention rules, or a cookie policy, so treat "privacy-friendly" as a stated design goal rather than a verified guarantee until you check the product's own documentation.

What "realtime" actually means here

The site frames its core difference as timing: "Most analytics tools tell you what happened yesterday. Open Analytics helps you understand what is happening right now."

Concretely, the page says you can:

• Watch visitors arrive live from around the world
• See who is visiting right now, what pages they are viewing, where they came from, and how they move through your website
• Use an interactive visitor map
• See live visitor context such as a page and country — the page gives the example: "silent yak is live on /pricing from United States" — Live visitor · Google Search

That last example shows the realtime view combining three things at once: an active session, the page being viewed, and the source (Google Search). This is what makes it useful for spotting traffic as it lands instead of reviewing it the next day.

How the tracking is set up

Realtime data depends on the script being installed correctly. The site describes a three-step flow:

1. Create a project — Sign in with Google or GitHub, then create a website in the dashboard. Each project gets a site key, and the page notes there is "no separate analytics database to provision."
2. Add the script — Copy one script tag into your HTML or Next.js layout.
3. Events flow — The page states events POST to your Open Analytics server and land in your PostgreSQL database.

The practical implication: because events go to your own server and PostgreSQL database, the data path is under your control rather than only sitting in a third-party analytics account. That is the mechanism behind the privacy-friendly framing — but the page does not specify what is stripped, hashed, or anonymized before storage, so verify that in the product docs if it matters for your use case.

What you can track beyond realtime

Realtime is one part of a broader set. The page lists:

The public dashboard point is worth noting for privacy: viewers see analytics without needing an account, so decide deliberately what a shared dashboard exposes before publishing it.

Who it is aimed at

The page positions the product "for founders, not analysts" — focused on visitors, conversions, traffic sources, campaigns, and SEO performance rather than "dozens of reports you'll never use." If your need is deep custom reporting or warehouse-level analysis, that framing suggests it is not the target use case.

Access and trial conditions

Per the page:

• Startup plan — free for 1 year, up to 100 projects; the page also says "Startup plan free to apply"
• Paid plans — 14-day free trial
• A live demo is available ("View live demo")

The page does not list prices or payment platforms, so do not assume paid-tier costs or billing details from this description alone.

Practical checks before committing

Because the privacy claim is central but lightly specified, confirm these directly in the product before relying on it:

• What visitor data is stored, and in what form
• Whether cookies or local storage are used, and whether a consent banner is needed in your jurisdiction
• Retention and deletion controls for the PostgreSQL data you host
• What a public dashboard reveals to unauthenticated viewers

If those answers match your requirements, the realtime view plus self-hosted event storage is the combination that distinguishes it from conventional historical-report analytics.

Open Analytics (analytics.gitopen.dev) is a realtime, privacy-friendly website analytics tool. Setup takes three steps: sign in with Google or GitHub, create a project to get a site key, and paste one script tag into your HTML or Next.js layout. Events then POST to the Open Analytics server and land in a PostgreSQL database — you don't provision a separate analytics database yourself. The Startup plan is free to apply for one year with up to 100 projects; paid plans come with a 14-day free trial.

Before you start

• A Google or GitHub account for sign-in.
• Access to your site's HTML, or your Next.js layout file if you use Next.js.
• No database setup on your side — each project gets a site key, and there is no separate analytics database to provision.

Step 1: Create a project

Sign in with Google or GitHub, then create a website in the dashboard. Each project is issued a site key that identifies where its events come from.

Step 2: Add the script

Copy the single script tag into your HTML, or into your Next.js layout. This one embed is the whole integration — there is no SDK to install or config file to write.

<!-- Paste the script tag from your project dashboard -->
<script src="https://analytics.gitopen.dev/script.js" data-site-key="YOUR_SITE_KEY"></script>

For Next.js, place the same tag in your layout so it loads on every page.

Step 3: Verify data is flowing

After deploying, open your site in a browser and check the dashboard. Events POST to the Open Analytics server and flow into PostgreSQL, so you should see activity appear in realtime rather than after a batch delay. The live visitor view shows who is on the site right now, which pages they're viewing, and where they came from — for example, a visitor arriving from Google Search on /pricing.

What you can track once it's live

You can also create public dashboards to share analytics with clients, teammates, investors, or your community — viewers don't need to log in.

Common snags

• No data after deploying: confirm the site key in the script tag matches the project, and that the tag is present on the pages you expect to track.
• Next.js pages missing events: the tag needs to be in the layout, not a single page, so it loads site-wide.
• Sharing access: use a public dashboard instead of handing over account credentials, since viewers don't need a login.

Who this fits

Open Analytics is aimed at founders rather than analysts: the focus is visitors, conversions, traffic sources, campaigns, and SEO performance, without dozens of unused reports. If you mainly need historical reporting and deep custom analysis, a heavier analytics suite may suit you better. If you want realtime visibility and a one-script setup, this gets you there in minutes.

Open Analytics is a website analytics tool that tracks visitors, pageviews, sessions, bounce rate, and realtime activity, positioned as simple, fast, and privacy-friendly. It fits teams that want to see traffic as it happens and connect analytics with SEO signals, rather than dig through historical reports built for dedicated analysts. The site describes a free Startup plan (1 year, up to 100 projects) and a 14-day free trial on paid plans.

What it does

Open Analytics focuses on live behavior and growth sources rather than yesterday's numbers. According to the site, the core capabilities are:

• Realtime analytics — watch visitors arrive live, see which pages they are on, where they came from, and how they move through the site, including an interactive visitor map.
• Traffic source tracking — traffic sources, campaigns, referrals, and organic search performance in one place, so you can see which channels bring visitors that matter.
• SEO insights alongside analytics — Domain Authority tracking, Search Console data, and SimilarWeb insights without switching between tools.
• Search engine visibility — monitor crawl activity, search engine bots, and indexing behavior, including when Google discovers, revisits, or ignores content.
• Public dashboards — share analytics with clients, teammates, investors, or a community without requiring viewers to log in.

The stated audience is founders, not analysts: the emphasis is on visitors, conversions, traffic sources, campaigns, and SEO performance instead of dozens of unused reports.

How setup works

The site describes a three-step flow:

1. Create a project — sign in with Google or GitHub, then create a website in the dashboard. Each project gets a site key, and no separate analytics database needs to be provisioned.
2. Add the script — copy one script tag into your HTML or Next.js layout. Events POST to your Open Analytics server.
3. Start reading data — events flow into your PostgreSQL database, and traffic appears in the dashboard.

The site claims setup in about one minute. The practical implication of the PostgreSQL detail: your event data lands in a database you control, which is relevant if data ownership or querying raw events matters to you.

Plans and access

The page does not list prices, payment methods, or login restrictions beyond the sign-in options above, so check the site's pricing page for current terms before committing.

When it is a good fit

Choose Open Analytics if you want realtime visitor visibility, SEO signals in the same place as traffic data, and shareable dashboards without giving viewers accounts. It is less suited if you need deep historical reporting, complex attribution modeling, or analyst-grade segmentation — the product explicitly positions itself away from that.

To evaluate it, the fastest path is the live demo linked from the site, then the free Startup plan for a real project.

Open Analytics (analytics.gitopen.dev) puts traffic analytics and SEO signals in the same dashboard, so you can see not just how many people visit but how they found you and how search engines treat your pages. According to the site, it combines website analytics with Domain Authority tracking, Search Console data, and SimilarWeb insights "without switching between multiple tools," and it also monitors crawl activity, search engine bots, and indexing behavior. This is useful if you want one place to connect acquisition channels with search visibility — but note that the site describes these as combined capabilities rather than detailing exactly how each data source is synced.

What each side covers

The point of combining them is to answer questions that a single tool can't: which channel brings visitors that matter, and whether search engines are actually discovering and revisiting the content you publish.

How the pieces work together

Traffic sources and organic search in one view

The site says you can "track traffic sources, campaigns, referrals, and organic search performance in one place" and "understand which channels bring visitors that matter." So instead of reading a traffic report in one tool and a search report in another, you compare them side by side.

Search Console and third-party SEO data

Search Console data and SimilarWeb insights are pulled in alongside your own analytics, plus Domain Authority tracking. This lets you connect what visitors do on-site with how your domain and search presence look externally.

Crawl and indexing monitoring

Open Analytics monitors crawl activity, search engine bots, and indexing behavior, with the stated goal of knowing "when Google discovers, revisits, or ignores your content." That turns indexing from a guess into something you can watch.

A concrete example

Say you publish a new page. In one dashboard you could check whether Googlebot has crawled it, whether it's indexed, what Domain Authority and Search Console data say about the domain, and — once traffic arrives — whether those visitors came from organic search, a referral, or a campaign. If the page is crawled but ignored, or indexed but getting no organic traffic, the combined view points you toward the likely cause faster than checking each signal separately.

Setup context

The site describes a three-step flow: sign in with Google or GitHub and create a project (each gets a site key, with no separate analytics database to provision), paste one script tag into your HTML or Next.js layout, and events flow into your PostgreSQL database. Realtime tracking and the visitor map then show activity as it happens. The site claims setup in about one minute.

What to keep in mind

• The site presents these as combined features; it does not specify how Search Console or SimilarWeb data is authenticated or how often it refreshes, so verify that in the product before relying on it.
• A Startup plan is described as free for 1 year (up to 100 projects), and paid plans offer a 14-day free trial — check current terms on the site, since pricing details aren't fully specified here.
• Public dashboards can be shared without viewers needing to log in, which is handy for showing SEO and traffic progress to clients or teammates.