Skip to content
ABOUT US

Czech sGTM hosting, built transparently.

DataNostro is run by a small team in Brno. The servers run in an EU Tier III data center (Germany), we invoice in CZK, and we write the code ourselves. This page tells you who's behind it, where it runs, what the continuity plan is — and the current raw numbers.

Who runs it

Jan Malatinský

Founder · leads product, infrastructure, and support

Before DataNostro I spent ten years building tracking for Czech stores and agencies. We handled sGTM with foreign managed vendors and self-hosted in the cloud, and in both cases we hit the same things: invoices in dollars or euros, slow deploys, no native Sklik / Heureka, support in a different time zone and in English. DataNostro was created so I could solve these problems for myself and for the teams I work with.

I'm reachable directly. When you open a ticket with DataNostro, most days it's me who answers — not a first-line outsourcer in another country. For large clients that's a weakness (no 24/7 NOC); for small and mid-sized companies it's usually a plus (I understand your configuration, not just the FAQ).

  • 📧 [email protected]
  • 📍 Brno, Czech Republic
  • 🇨🇿 Sole trader — company ID shown on the invoice and in the commercial register

Where it runs

No vague "EU cloud". Named servers in named data centers, GDPR-clean, with no data transfer outside the EU for running the tracking pipeline.

Hosting

An EU Tier III data center (Hetzner, Germany). We've signed their DPA; Hetzner itself holds ISO 27001 and ISO 9001. The full list of sub-processors is in our DPA.

Backup: a second EU region, daily pg_dump.

DNS / TLS / DDoS

Cloudflare (USA + global PoP) only for the datanostro.com domain and TLS termination. Tracking-pipeline data is in transit, not stored.

Cloudflare holds SCC EU 2021, SOC 2 Type II, and ISO 27001 (their own certifications, not DataNostro's).

Stack

Django 5.2 LTS · PostgreSQL 16 · PgBouncer · Redis · Celery (gevent) · Go ingress μservice · nginx · Docker. All open-source, no vendor lock-in.

Email and billing

Transactional emails via SMTP Seznam.cz (CZ). We generate the invoices ourselves, ISDOC 6.0.2 for Pohoda / Money / ABRA, no third-party billing payment processor.

→ Full list of sub-processors in the DPA

What happens if the team stays small or I leave

Auditors rightly ask about the bus factor for sGTM hosting. We'll say it plainly: today, operations are carried by a small team and the founder. Here's how we handle that situation so it doesn't put you at risk.

  • You can download your data as a ZIP anytime

    The dashboard has /dashboard/export/ — the entire tenant configuration, events, GTM workspace JSON, invoices. No waiting, no support ticket. If you ever get tired of us, you'll have everything in hand within an hour.

  • No proprietary format

    The sGTM container is a standard Google image. The GTM workspace is standard JSON. Migrating from us to any other managed host, your own server, or the cloud takes hours — not weeks. We have a migration wizard right in the dashboard.

  • Operations are 95% automated

    Deploying new containers, DNS verification, SSL renewal, billing, monitoring, alerting — it all runs in Celery Beat. Even if the founder doesn't log in for a week, invoices get issued, containers restart, alerting works.

  • Source escrow for Enterprise

    For clients on the ENTERPRISE plan, the contract can include source-code escrow via a notary — if DataNostro ceases to exist, the client gets access to the code to take over operations themselves. Details in the contract.

  • Backups in an EU region and offline

    A daily pg_dump to a second EU region. A monthly offline copy. Retention 30 days (daily) / 12 months (monthly). The full DR plan is available for Enterprise clients to review.

What's been running since when

  1. 2025 Q3
    Prototype

    The first version of the sGTM hosting for the founder's own projects.

  2. 2025 Q4
    Internal beta

    Multi-tenant dashboard, automatic CZK invoicing, ISDOC export, native Sklik / Heureka connectors ready for public launch.

  3. 2026 Q1
    Public launch

    Open registration, a public status page, a 99.9% SLA, a knowledge base, a migration wizard from previous solutions.

  4. 2026 Q2
    Refinement and transparency

    Go ingress μservice (sub-ms latency), 90-day uptime bars, strengthened legal documents, capacity alerts, self-service account cancellation.

  5. Planned
    Roadmap

    BigQuery / Firestore service-account UI, Schedule Requests, Request Delay, per-tenant IP block, mobile SDK, an external security audit (ISO 27001 readiness — refined based on Enterprise client demand). → Public roadmap

Let's get on a call

For companies over 1M requests a month, reach out directly — we'll set up a video call and show you the dashboard live. We build the platform from the ground up and take every onboarding personally.

Write to the founder Contact form