NordaxIT

Software development company · Klaipėda, Lithuania

Your next release, shipped by a senior team in Lithuania.

We build websites, web platforms, mobile apps and back-office automation for companies across the EU — fixed scope, a written price before we start, and everything in your own repository from day one.

You talk to the engineer who would lead the build — not a salesperson.

to a written scope and fixed price
24hto a written scope and fixed price
to the first build you can click
5 daysto the first build you can click
same working day as your team
CETsame working day as your team
From first call to working softwareHOW WE START
  1. DAY 1
    Technical call, 30 minutes
    Goals, constraints, existing systems
  2. DAY 2
    Written scope & fixed price
    Milestones, exclusions, assumptions
  3. DAY 3
    Kick-off, environments live
    Repository and hosting in your accounts
  4. DAY 5
    First build you can click
    Real staging URL, not a mockup
Most clients come to us after an agency handed over something they could not maintain. We build the opposite of that.
Linas D.Founder, NordaxIT
Lithuanian company, reg. 307668471 — EU contracts, GDPR by defaultWorking across the EU — remote, in CET hoursFounded by engineers, still run by engineers

Three things we do, properly.

The same engineers design it, build it and keep it running afterwards.

Work we have shipped.

SAFA invoicing and VAT dashboard built by NordaxITOpen safa.lt →
Our own product · safa.lt

SAFA — invoicing and VAT filing on autopilot

We designed, built and operate SAFA end to end: invoices issued in seconds, incoming PDFs read and vendors verified through VIES, and i.SAF registers filed with the tax authority in one click.

Scope
Product · build · operations
Stack
Next.js · Postgres
Standard
VMI i.SAF v1.2
Open safa.lt →
Freight forwarding · Netherlands

Published transit times and live shipment tracking

A forwarder whose rates lived in email threads. Now every lane, transit time and indicative price is on the site, with container tracking and quote requests handled in one place.

Scope
Design · build · launch
Stack
Next.js · CMS · SEO
Self-service
Rates · container tracking
Hospitality · Japan

Direct bookings instead of platform commission

An eight-room townhouse losing margin to booking portals. A bilingual site with room rates, availability and direct enquiries, built to load fast on hotel Wi-Fi abroad.

Scope
Product · build · support
Stack
TypeScript · Postgres
Bookings
Direct, no commission

What you get, in writing.

Four commitments that go into every contract. They are the things clients tell us went wrong last time.

Ask for a sample scope document →

A fixed price before we start

Scope, milestones and price agreed up front. If we underestimate, that is our problem, not your invoice.

Your code, your accounts

Your repository, your cloud, your domains. Nothing is hostage if you decide to continue elsewhere.

Something to click, every few days

A working staging build, not a status report. You see progress instead of hearing about it.

The same people, start to finish

No handover from sales to delivery, no juniors billed as seniors, no rotating account manager.

Fair questions.

The things people ask on the first call, answered before you have to ask them.

Who will actually work on my project?

The engineer you speak to on the first call. We deliberately run a small number of projects at a time so the person who scoped your build is the person writing it, from kick-off to handover.

What if the scope changes halfway through?

Priorities change, that is normal. Anything new gets a price and a timeline impact in writing before we touch it — nothing is silently added to your invoice, and nothing important gets quietly dropped either.

How do you price work?

Fixed price per project after a written scope, or a monthly rate for ongoing support and product work. Baltic rates with senior-only staffing — typically well below Nordic and German agencies for the same seniority.

Can you take over a project someone else started?

Often, yes. We start with a short paid audit of the existing codebase and give you an honest read: what is salvageable, what should be rewritten, and what it will cost either way.

What happens after launch?

Thirty days of fixes are included. After that you can take a care plan — hosting, updates, monitoring and a block of changes each month — or take the documentation and run it yourself.

A brief today, scope and price tomorrow.