RomânăContact
Menu
Services

Admin panels that show what is really happening in your application

Every application we build comes with the panels needed to operate it: switch sources and features on or off, review what automated jobs did, watch AI costs, and read traffic statistics that separate people from robots. Built into the application, without third-party trackers.

Design your admin workflowExplore our work

When this service fits

  • You run software whose settings live in code or in someone’s head.
  • You need to see imports, jobs, conversations or costs without opening the database.
  • Your analytics count crawlers and AI agents as visitors and the numbers mean little.
  • You want visitor statistics without cookie banners or sending data to an analytics company.

What you receive

  • A configuration panel with its own login: features, sources, schedules and keys (stored encrypted).
  • Operational views for the data your app manages: catalogue, offers, conversations, alerts, jobs.
  • Daily statistics: unique visitors without cookies, page views, top pages, referrers, clicks.
  • Separate reporting for identified bots by name, robot clicks, and pages served but never confirmed by a browser.
  • Cost and usage views for AI and email providers, with alerts at thresholds.

Scoped separately

  • Enterprise role-based permissions, single sign-on and audit trails (possible, scoped as custom work).
  • CRM features and customer account management.
  • Business intelligence across external data warehouses.
Example from our own products

Statistics that tell people and robots apart

On our sites a page view counts only when the visitor’s browser confirms it with a small request after the page runs; pages sent but never confirmed are reported as “served, unconfirmed”. On one day on Raftul copiilor, that separated about 2,900 of 3,517 “pages” that were automated speed tests sent with a browser’s name. Robots are counted by name (Googlebot, bingbot and others).

On Cumpără cu AI, clicks to shops are a person’s only when they come from one of our pages in a browser that is not a robot. At one point a crawler began opening nearly every outbound link once a day: 500 to 2,900 clicks daily, against 2 to 84 before; those are now marked as robot clicks, kept for the network but excluded from rankings and reports.

Unique visitors are counted with a hash of address and browser type under a key held in memory and replaced every midnight, so nothing identifies a person and no cookie is needed. The panels also show imports, AI conversations and costs, search problems from real conversations and the configuration of networks, shops, categories and AI models.

Cumpără cu AI · Raftul copiilor

How the work runs

  1. Operations interview

    What you check daily, what goes wrong, who needs access.

  2. Metrics that matter

    Definitions written down: what counts as a visitor, a click, a success.

  3. Build

    Panels inside the application, protected, fast on large tables.

  4. Alerts

    Thresholds that notify you instead of waiting to be checked.

What affects cost and schedule

  • The number of entities and actions to manage.
  • Statistics requirements and data retention.
  • Access control: one admin or several roles.

Questions buyers ask

Is bot detection perfect?

No. A crawler that runs the page and hides its identity can still be counted as a visitor. We separate everything that identifies itself or behaves like a robot and document what the numbers can and cannot tell you.

Do your statistics need a cookie banner?

Our own statistics use no cookies and store only daily totals. Whether your site needs a banner depends on everything else it uses.

Related services

Design your admin workflow

Tell us what you need in a few sentences. NeedAI Studio answers personally, in English or Romanian.

Discuss your project