Custody of data that belongs to the buyer, and the terms that govern it
A database contract is a custody arrangement before it is a technical one. The buyer remains accountable for the data whatever the supplier does with it, so the terms that dominate are about control: where the data is physically held, which staff may access it and under what clearance, whether any processing happens outside the agreed jurisdiction, what the supplier may do with derived or aggregated data, and how quickly the buyer can get everything back in a usable form. Bidders who lead with platform features and treat these as annexes misjudge the evaluation.
Operationally the specification is about continuity and provability. Availability targets, backup frequency, and a recovery point and recovery time objective that are tested rather than asserted form the core; buyers increasingly require evidence of an actual restore, not a backup log. Performance is specified in terms the buyer can measure, such as response time at a stated concurrency, and capacity growth is priced in advance so that success does not become a renegotiation.
Migration bookends the contract and is where most of the risk lives. Bringing data in means extraction from a legacy system, cleansing, mapping, reconciliation and a proving period during which both systems run; taking it out again at the end means the same work in reverse, usually under time pressure. Tenders that specify the exit deliverable precisely -- format, schema documentation, referential integrity, the timescale and who pays -- produce contracts that can actually be competed again. Those that do not produce an incumbent that cannot be displaced.
This section describes how this category is bought generally, across the public buyers that publish it. The figures elsewhere on this page are measured for this market alone.
Who buys database management in Lithuania?
GlobalGov holds 84 database management records from 52 distinct buying organisations in Lithuania. The most frequent publishers are Valstybinė mokesčių inspekcija prie Lietuvos Respublikos finansų ministerijos (5 records); Viešoji įstaiga CPO LT (5 records); VšĮ Kauno technologijos universitetas (5 records); Vilniaus miesto savivaldybės administracija (4 records); Kauno miesto savivaldybės administracija (3 records); Kertinis valstybės telekomunikacijų centras (3 records). Between them the 6 largest account for 30% of everything published, so buying here is spread across many separate authorities.
| Buying organisation | Records | Share |
|---|---|---|
| Valstybinė mokesčių inspekcija prie Lietuvos Respublikos finansų ministerijos | 5 | 6.0% |
| Viešoji įstaiga CPO LT | 5 | 6.0% |
| VšĮ Kauno technologijos universitetas | 5 | 6.0% |
| Vilniaus miesto savivaldybės administracija | 4 | 4.8% |
| Kauno miesto savivaldybės administracija | 3 | 3.6% |
| Kertinis valstybės telekomunikacijų centras | 3 | 3.6% |
What are database management contracts worth in Lithuania?
33 of the 84 records publish a contract value. The median is $300,564 and the largest single published value is $6.4M. By size, 4 under $100k, 22 between $100k and $1M, 7 between $1M and $10M. The remaining 51 publish no value at all, so every figure here describes the priced subset only, and values are as stated by the buyer rather than as finally awarded.
| Contract size | Records | Share of priced |
|---|---|---|
| under $100k | 4 | 12% |
| between $100k and $1M | 22 | 67% |
| between $1M and $10M | 7 | 21% |
| above $10M | 0 | 0.0% |
How long do bidders get to respond to database management tenders in Lithuania?
Across the 44 Lithuania database management notices that publish both a publication date and a closing date, the median response window is 34 days. A quarter of them allowed 32 days or fewer and a quarter stayed open for more than 36. Not one of them closed within a fortnight of being published, so the window on this market is consistently workable.
How often are database management tenders published in Lithuania?
Lithuania published 5 notices in this category in the last twelve months. Over the last three years there were 54, spread across 41 separate months of activity since 25 June 2021. April is historically the busiest month. No new notice has been published in this category since 26 May 2026, 128 days ago, so treat the figures above as a record of the market rather than as this week's pipeline.
How does Lithuania compare with other database management markets?
Among the 21 countries where GlobalGov holds a comparable database management market, Lithuania ranks 8th by number of records. The largest is France (423 records against 84 here). Within Lithuania itself, database management is the 36th largest of the 52 procurement categories tracked here.
Where do the Lithuania database management records on this page come from?
These 84 records are collected from 1 official source: TED (84). GlobalGov is an independent aggregator and is not affiliated with any of them; each record links back to the notice on its issuing portal. The set is rebuilt nightly, and the counts on this page were taken on 2026-10-01.
Most recent Database Management tenders in Lithuania
None of these are open for bids now — they are the most recent records GlobalGov holds for this market, kept here so the shape of a typical database management notice in Lithuania is visible. Set an alert to be told when the next one opens.
Lithuania – Data services – Automatizuotos blaivumo patikros su biometriniu veido atpažinimu sistemos paslaugos
Lithuania – Data storage services – VIEŠOSIOS DEBESIJOS PASLAUGOS
Lithuania – Data analysis services – (2024-U4) Duomenų surinkimo ir analizės informacinės sistemos (DSAIS) analizės, įvertinimo ir analitinių ataskaitų suformavimo paslaugų pirkimas
Other procurement categories in Lithuania
Database Management procurement in other markets
Never Miss a Lithuania Government Contract
Finding Lithuania tenders usually means a local portal, a local registration and someone who reads the language. Get an alert you can read when a new database management opportunity is published there.
Start Free Trial