Narva, Estonia · EU
Established in Narva, Estonia. 1PT Grupp Osaühing designs and builds custom software, scalable cloud infrastructure and system integrations for European businesses and institutions — under a written service agreement, in stages, with the source code and pipelines handed over at the end.
1PT Grupp OsaühingVerify in the public register
Companies, public institutions and technology teams, under a written service agreement governed by Estonian law. We do not provide remote technical support to consumers, do not repair devices and do not recover accounts or passwords on anyone's behalf.
Full company details and register data →Six answers produce an indicative delivery window and the workstreams behind it. Everything is calculated in your browser — nothing is sent to us unless you choose to submit an enquiry.
Indicative delivery window
13–19 weeks
6 workstreams · model v1
Architecture layers
Workstreams
Standard business data: GDPR baseline: lawful basis recorded, retention set, access controlled.
Indicative planning output based on the answers given. Not a quotation, not an offer, and not a delivery commitment. Scope, effort and price are fixed only in a signed written agreement.
Take this scope to an enquiry// core services
Each one is scoped and contracted separately. If a piece of work spans more than one, it is sequenced rather than bundled.
Web, mobile and enterprise applications built to a written specification.
Bespoke business systems designed around your domain rather than around a template: data model, backend services, web or mobile interface, and an automated test suite that runs on every commit.
Read the detail →An independent read of the estate you have, and a target design you can sequence.
A structured assessment of an existing system landscape — code, data, infrastructure, delivery process — ending in a written target architecture and a change sequence a team can actually execute.
Read the detail →Environment topology, infrastructure as code, pipelines and observability.
Moving workloads to cloud infrastructure without moving the existing problems with them: a documented target topology, infrastructure defined as code, a deployment pipeline with a rehearsed rollback, and monitoring that fires before a customer notices.
Read the detail →Replace an ageing system in stages, without a big-bang rewrite.
Incremental replacement of software that still earns its keep but has become expensive to change: an interface seam is introduced, components move across one at a time, and the old system keeps running until the last one has.
Read the detail →// how we work
Every engagement starts with a document: what is being built, what is out, the assumptions behind the estimate, and how we will both know it is finished.
Delivery is broken into stages that each end with something running. Stop at the end of any one of them and everything delivered so far is yours, working.
Source code, infrastructure definitions, pipelines and runbooks transfer to your accounts. No delivered system depends on this company continuing to exist.
01
A call or a meeting, no charge, no obligation. We want the problem in your words, the constraints you are already under, and who has to agree to a change before it can happen.
02
What is being built, what is explicitly out, the assumptions the estimate rests on, and how we will know it is finished. If we think the request as stated is the wrong thing to build, this is where we say so.
03
A written service agreement under Estonian law: scope, stages, acceptance criteria, intellectual property, confidentiality, and a data-processing annex where personal data is involved.
04
Each stage ends with something running in an environment you control, plus the tests that show it behaves. You can stop at the end of any stage and keep everything delivered so far.
05
Source code, build pipeline, deployment scripts and a runbook, transferred to your accounts. Support afterwards is a separate agreement, never an automatic renewal.
// recurring problems
Described as the problem rather than as a product, because the right answer differs every time.
Problem — Two systems that both hold the truth about a customer, kept in step by people re-typing things, and a monthly argument about which one is right.
Approach — One integration gateway owns the contract between them. Messages are versioned, failures are retried and then parked for a human, and a nightly reconciliation report names every record that drifted.
Problem — A system that still runs the business but that nobody wants to touch: unsupported runtime, no tests, and one person who understands the deployment.
Approach — A seam in front of it, tests written against observed behaviour before anything moves, then component-by-component replacement. The old system stays live until the last component has moved across.
Problem — Reporting built on spreadsheets exported by hand, where two departments produce two different numbers for the same question.
Approach — Sources mapped and ingested on a schedule, a dimensional model with definitions written down, and a reporting layer where every figure traces back to the row it came from.
Problem — A process running on email threads and a shared spreadsheet, where the state of any given case is whatever the last person remembers.
Approach — The process modelled explicitly — states, transitions, who may do what — with an interface built for the people who use it all day rather than for a demo.
1PT Grupp Osaühing supplies IT consulting and software engineering to organisations under a written service agreement. To be unambiguous about the boundary, these are services we do not provide at all:
If you have arrived here looking for help with a personal device, an account you cannot access, or a support call you were told to make, this company is not the right place and cannot assist.
// questions
1PT Grupp Osaühing works with companies, public institutions and technology teams only, under a written service agreement. We do not supply services to consumers, do not provide remote technical support for home computers, do not repair devices, and never make unsolicited support calls.
In Estonia. 1PT Grupp Osaühing is entered in the Estonian Business Register under registry code 11481296, registered on 10.04.2008, with its registered office at A. Puškini tn 43, 20609 Narva, Ida-Viru maakond, Estonia. The EU VAT number is EE101404152 and both can be checked in the public registers linked from every page of this site.
With a scoping conversation, at no charge. If the work is a fit, the next artefact is a written scope — what is being built, what is out of scope, the assumptions behind the estimate, and the acceptance criteria. Work begins after a signed agreement, never before.
A delivery window and a workstream breakdown, derived from the answers you give it. It is a planning aid, not a quotation: it produces no price, and nothing it shows is binding on either side. Scope and price are fixed only in a signed written agreement.
The client, on handover, as set out in the service agreement. That includes source code, infrastructure definitions and deployment scripts. We keep no licence back that would let us withhold a delivered system.
They are used to answer your enquiry and to record it. The lawful basis is GDPR Art. 6(1)(b) — steps taken at your request before entering into a contract — so no consent is asked for or relied on. Enquiries that do not lead to an engagement are deleted after 24 months, and you can ask for yours to be removed sooner by writing to privacy@oneptgrupposauhing.com.
English, Estonian, Russian. Contracts and specifications are produced in English or Estonian.
Send the scope and we will reply within one business day. The first conversation costs nothing and does not create a contract — 1PT Grupp Osaühing works only under a signed written agreement.