Website Traffic Analytics and MySQL Tools

This release improves the tools around a running project: understanding where visitors come from, inspecting databases, keeping MySQL data backed up, and working with blog images faster.

The theme is visibility. Once an app is live, builders need to see traffic, data, and content without leaving the dashboard for a pile of separate tools.

Traffic Sources by Page

Project analytics now include a page-by-source view.

For each page, VibeNest can show how many visitors arrived and where they came from. Sources are grouped into useful channels such as Organic, Social, Referral, Direct, Internal, and Campaign. The table can distinguish sources like Google, Twitter/X, Telegram, Product Hunt, Reddit, direct traffic, and UTM campaigns.

The same source classification feeds both application code and ClickHouse queries, so the grouped view and unique counts are produced consistently at query time.

This is visible inside a project as Traffic by page and in broader internal traffic views.

Account-Wide Analytics and Platform Traffic

The account analytics page now has a project filter. Builders can look across all projects or narrow the same analytics surface to a single project without opening each project one by one.

The dashboard also separates Wiki and Live App views and keeps source, geography, technology, and campaign slices available at the account level.

VibeNest now tracks traffic to the platform itself too, including pages such as the homepage, pricing, and blog. That closes a blind spot at the top of the funnel: visits to vibenest.net are now measurable instead of disappearing before a user reaches a project.

UTM values are normalized to lowercase when stored, which prevents G2 and g2, or Twitter and twitter, from splitting into separate rows.

MySQL Console in the Dashboard

The database console added earlier for Postgres and SQLite now covers managed MySQL.

From the Storage tab, the owner can open a temporary Adminer console for the managed MySQL database. It runs behind per-session credentials, an unguessable subdomain, owner checks, and browser authentication. Like the Postgres console, it is embedded in the dashboard and stops when idle.

This gives MySQL projects the same practical workflow: inspect tables, run queries, and debug data without exposing the database publicly or setting up SSH and port forwarding.

The implementation now uses a prebuilt console image, so opening the console does not rebuild the tool container every time.

MySQL and MariaDB Backups for Compose Projects

Compose backups now support MySQL and MariaDB in addition to Postgres and Qdrant.

The backup sidecar can detect a MySQL-compatible service, use the project's configured database access, run mysqldump, and restore through mysql. This brings MySQL compose stacks closer to parity with Postgres: backup, restore, and storage in the VibeNest backup path.

The backup flow was validated against a real MySQL 8 round trip. That mattered because the default MySQL 8 authentication plugin required an extra connector package; a superficial dump path would have failed on a common production setup.

Daily check digests also became less noisy. The same daily digest is deduplicated by UTC day and content hash, so restarts do not resend identical health summaries.

Drag-and-Drop Images in Blog Editing

The blog editor now accepts image drops directly on the Content field.

Dropping one or more images uses the same upload path as the existing Insert images button, then appends Markdown image references to the post. The drop zone highlights during dragover and works for both the platform blog and project blogs.

This deliberately reuses the existing internal upload path instead of a raw asset API call, which keeps platform-blog permissions working correctly.

What This Means for Builders

Project owners can answer more questions from inside VibeNest:

which pages bring traffic and from which sources;
whether traffic is coming from campaigns, search, social, referrals, or direct visits;
what is inside a MySQL database right now;
whether MySQL compose data is being backed up;
how to add images to a blog post without leaving the editor flow.

The result is a dashboard that is less about only deploying the app and more about operating it after it is live.