GovRadar
GovRadar is a German web platform that helps public-sector buyers prepare tenders. Its GovBot assistant drafts specifications, criteria matrices and contracts from millions of real procurement files, keeping every step documented and auditable.
What is GovRadar?
GovRadar is a German web application built for one job: preparing public tenders. It is sold to contracting authorities of every size, from municipalities and districts to state ministries, municipal utilities, hospitals, universities, fire services and the Bundeswehr, and the vendor claims more than 600 administrations already use it.
The starting point is a shift in German procurement law. Value thresholds have risen and procedural obligations have fallen away, which leaves buyers more discretion but also heavier duties to document and justify what they decide. GovRadar's answer is a single workspace, the Beschaffungsvorhaben, in which the requesting department, the procurement office and the legal team work on the same documents instead of trading versions by e-mail.
Inside it sits GovBot, the AI assistant. What separates it from a general-purpose language model is its source material: rather than drawing on general training knowledge, it works from millions of published tender documents issued by more than 16,000 public bodies and gathered from over sixty procurement platforms, among them the federal e-Vergabe portal, the state and municipal platforms and bund.de. GovBot proposes structure and wording for a specification, checks the text for missing content, duplication and contradictions, and displays the origin of every suggestion so the author can verify it. Where context is missing it inserts a placeholder to be completed by hand instead of inventing one.
Around the assistant sit the pieces a tender actually needs. An AI topic overview maps the requirement dimensions that should be covered, filterable by administrative level or publication date. Market exploration searches a supplier database of more than two million companies and a manufacturer-neutral catalogue of more than nine million products. Exclusion and award criteria are built with weightings and scoring logic into an evaluation matrix that lands directly in the tender documents. EVB-IT contract templates are included, and organisations can import their own.
Everything is versioned: earlier states can be reopened and the history records when a document was downloaded, which is the point for an authority that may have to defend a decision years later. GovRadar runs in the browser, is certified to ISO/IEC 27001:2022, is hosted in Germany and follows BITV 2.0 and WCAG 2.1 level AA.
What it does
- Draft a tender specification with the GovBot assistant, with the source shown for every suggestion
- Get an AI topic overview of the requirement dimensions a specification ought to cover
- Explore the market across more than two million companies and nine million products
- Build exclusion and award criteria with weightings and scoring logic into an evaluation matrix
- Search published tenders drawn from more than sixty public procurement platforms
- Generate contracts from the built-in EVB-IT templates or from your own imported ones
- Track versions, approvals and downloads so each step can be justified in an audit
When to use GovRadar / When not to
A quick filter to help you decide if GovRadar is the right fit.
When to use GovRadar
- Procurement offices in German municipalities, districts, state and federal authorities that must be able to justify every decision afterwards
- Subject-matter departments asked to write tender specifications without any procurement-law expertise of their own
- Public buyers in North Rhine-Westphalia and in ProVitako member municipalities, who can use the software without running a tender for it
- Buyers working for municipal utilities, hospitals, universities, fire services and the Bundeswehr, all named as customers on the site
- Teams that want to stop shuttling between Word files, e-mail threads and a separate procurement management system
When not to use GovRadar
- Organisations that need a published price or a free trial before committing: GovRadar quotes individually, on a twelve-month default term
- Teams looking for an API or ready-made connectors, since none is published and the product is deliberately browser-only
- Buyers working outside German procurement law, because the document corpus, the EVB-IT contract templates and the interface are all German
- Private-sector purchasing departments, as both the content base and the contractual framework are built for public contracting authorities
- Anyone expecting a legal guarantee: the vendor explicitly does not warrant that a product-neutral specification complies with procurement law
How to use GovRadar
A typical end-to-end flow, from setup to results.
- Identify your access route first: authorities in North Rhine-Westphalia draw on the state-funded licence, ProVitako members call off the framework agreement, everyone else goes through a sales conversation
- Request a demo through the demo video page, or ask for a strategy conversation via the contact form
- For the NRW licence, write to nrw@govradar.net to claim the entitlement financed by the MHKBD ministry
- Otherwise accept an individual offer; the contract runs for twelve months unless something else is agreed
- Have GovRadar open your access, which is granted on request or by invitation from your own organisation
- Sign in through the central authentication service and open the application in your browser; personal named accounts are mandatory and shared mailboxes are refused
- Create a Beschaffungsvorhaben, the shared workspace in which a single procurement project lives
- Draft the specification with GovBot and the AI topic overview, narrowing the research with topic, level and year filters
- Add exclusion and award criteria with their weightings, then pull in the EVB-IT contract templates or your own
- Assign tasks, invite colleagues and external contributors with read, comment or write rights, and export the finished documents
Pros & Cons
Pros
- Generation is grounded in a corpus of real tender documents, and GovBot shows the source of each suggestion instead of simply asserting it
- ISO/IEC 27001:2022 certification held by GovRadar itself, with a stated scope covering development, sales and operation of the SaaS solution
- Data hosted in Germany on Microsoft Azure in Frankfurt, with processing confined to the European Union
- An unconditional commitment not to train AI models on customer content, stated twice in the Trust Center
- Contract templates published for inspection before purchase: EVB-IT Cloud, SaaS framework agreement and the Article 28 processing agreement
- Two procurement routes that avoid running a tender of your own, through the state-funded NRW licence or the ProVitako framework agreement
- A detailed accessibility statement to BITV 2.0 and WCAG 2.1 AA that names its own remaining shortcomings rather than glossing over them
Cons
- No published price at all: the fee comes from an individual offer, on a twelve-month term that renews automatically unless cancelled three months ahead
- Neither a permanent free plan nor a free trial is advertised anywhere on the site
- No API and no named third-party integration; the product is closed and browser-only by design
- Scope is tied to German procurement law, and usefulness or availability outside Germany is undocumented
- Liability is capped at EUR 5,000 per incident and limited to what the vendor's insurance covers
- The vendor does not guarantee that the product neutrality of a specification complies with procurement law
- The published subprocessor picture is partial: only HubSpot is named as an Article 28 processor, with Azure disclosed separately in the Trust Center
Pricing & Plans
GovRadar publishes no price. There is no pricing page on the site, the paths /preise and /pricing return exactly the same 404 as any non-existent address, and the sitemap lists none. Under the general terms the fee follows from the price and services schedule in force and from the individual offer the customer accepts, with the amount and the due date set by the chosen service package. No permanent free plan and no free trial are advertised. The default contract term is twelve months, renewing automatically for a further year unless terminated three months before expiry. Two routes remove the cost at the point of use: in North Rhine-Westphalia the licence is financed entirely by the state, and ProVitako members call off an existing framework agreement. A comparison page shows figures of 0, 8 and 16 per month, but these carry no currency, sit in an unedited pricing-card module and do not represent what GovRadar costs.
Data, GDPR & hosting
A consolidated view of how GovRadar handles your data.
GDPR overview
Implementation is concrete rather than declaratory. GovRadar GmbH is established in Munich, so the GDPR and the German BDSG apply directly, and the site states GDPR compliance in plain terms. A data protection officer is appointed and reachable at datenschutz@govradar.net. The privacy notice gives a legal basis for each processing operation and lists data subject rights individually, citing Articles 7(3), 15, 16, 17, 18, 19, 20, 21 and 77, together with the competent Bavarian supervisory authority. A model Article 28 processing agreement is published in the Trust Center alongside the EVB-IT Cloud and SaaS framework templates. Transfers outside the EU are confined to HubSpot's US parent and to LinkedIn, covered by standard contractual clauses and the EU-US Data Privacy Framework. No Article 27 representative is named, and none is required of a controller established in the Union.
Who owns the data?
Ownership follows the GDPR split. For everything users type into the software the customer organisation is the controller and GovRadar acts only as a processor, under a separate Article 28 agreement. GovRadar is a controller in its own right only for account, login and log data, which it needs to run and secure the service. Documents and results handed over become the customer's property on delivery, together with simple rights of use, and the customer may keep using, altering or exploiting them after the contract ends, either in-house or through third parties. Customer organisations are held apart by strict logical tenant separation, so no access between them is possible.
Reuse rights
Yes, without asking. The general terms transfer ownership of every document, draft, specification and note GovRadar delivers to the customer at the moment of handover, together with simple rights of use, so no further permission is needed. The customer may go on using, modifying or commercially exploiting those results once the contract has expired, alone or through third parties. GovRadar's own licence runs the other way and is narrow: customer content is processed solely on the customer's instructions, never for the vendor's own purposes, and explicitly never to train AI models. Performance and usage data feed product improvement only after aggregation and anonymisation, from which no individual user, organisation or document can be reconstructed.
Data retention & training
Hosting summary
GovRadar states that the software is hosted in Germany on Microsoft Azure in the Frankfurt region, and that processing takes place exclusively within the European Union, primarily in German data centres. Infrastructure providers are chosen against a minimum bar: certification to at least ISO/IEC 27001 and attestation against the C5 basic criteria of the German Federal Office for Information Security. Customer organisations are separated logically, so no access or exchange between them is possible. The marketing site and CRM run on HubSpot Germany GmbH in Berlin, with storage on servers inside the European Union; where access by the US parent HubSpot Inc. cannot be excluded, the transfer rests on standard contractual clauses and the EU-US Data Privacy Framework. The site uses SSL/TLS encryption. The jurisdiction is German throughout: the vendor is established in Munich, German law applies, and Munich is the agreed place of performance and jurisdiction.
Things to keep in mind
Risks and trade-offs to weigh before adopting GovRadar.
- Over-reliance on suggestion: when a specification largely writes itself from precedent, the temptation is to sign off wording nobody has genuinely read. GovRadar shows sources and inserts placeholders precisely because the human check is still expected
- Precedent breeds conformity: drafting from millions of past tenders can quietly reproduce the assumptions, and the incumbent suppliers, of those tenders
- The vendor states that the procurement-law compliance of product neutrality is not a guarantee, so a specification that looks safe may still be challenged
- Accountability does not transfer: users remain solely responsible for the accuracy and completeness of what they enter, and GovRadar does not check content for legal correctness
- An audit trail cuts both ways, since the same documented history that defends a decision also records every revision and every download
- Skill erosion: teams that stop drafting specifications by hand may lose the judgement needed to notice when the assistant is wrong
- Commercial lock-in: with no published price, automatic annual renewal and three months' notice, leaving is a dated decision rather than an open one
Setup & Integrations
Technical difficulty
Very low. GovRadar runs in the browser and the vendor states there is no installation or integration effort and that it can be used immediately, without an IT project. Access is opened by GovRadar on request or by invitation from the customer organisation, and users sign in through a central OpenID Connect service. The only real constraint is administrative rather than technical: accounts must be personal and named, so shared functional addresses such as info@ or poststelle@ are refused and may be blocked. Step-by-step guidance for the main functions is built into the application itself.
Deployment
Supported languages
Behind GovRadar
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
What is GovRadar in one sentence?
What is the core of the software?
Where does the tender data come from?
Is my content used to train AI models?
Where is the data hosted?
What certifications does GovRadar hold?
How much does GovRadar cost?
Is there an API?
How are different customers' data kept apart?
How accessible is the application?
Should you pick GovRadar?
GovRadar is a narrow tool that knows exactly how narrow it is. Everything about it — the corpus of German tender documents, the EVB-IT contract templates, the vocabulary of the interface — is bound to German public procurement, and there is no attempt to pretend otherwise. Within that scope it is unusually well equipped.
Its real differentiator is not that it uses AI but where the AI gets its material. GovBot works from published tenders rather than general training knowledge, shows the source of each suggestion, and inserts a placeholder when context is missing instead of filling the gap. For an authority that may have to defend a specification years later, being able to trace a sentence back to its origin matters more than fluency.
The compliance groundwork is solid and, more importantly, checkable. The ISO/IEC 27001:2022 certificate is held by GovRadar itself with a stated scope, hosting is in Germany with processing kept inside the EU, the commitment not to train on customer content is unconditional, and the contract templates are published before anyone has to sign. The accessibility statement even lists what still does not work. Institutional validation is real too: a state licence financed by North Rhine-Westphalia and a ProVitako framework agreement are procurement decisions taken by people who had to justify them.
The reservations are commercial rather than technical. Nothing about the price is public, there is no trial, and the contract runs twelve months with automatic renewal, so evaluating GovRadar means talking to sales before knowing what it costs. The absence of any API or integration will matter to IT departments that expected to connect it to something. Neither is disqualifying for a public buyer used to framework agreements — but both deserve to be settled before a demo turns into a signature.
- Choosing a selection results in a full page refresh.
- Opens in a new window.