TECKNIKAITS TECKNIKAITS
Home / Services
What we do

From a written use case
to software you keep.

Every engagement starts the same way: translate a real customer problem into a written use case, then build exactly what solves it — nothing templated. Most of what comes out is software: web applications, APIs, desktop clients and the integrations between them. Some of it is a machine.

How an engagement runs
01
Tell us the problem

The problem and the constraints, in your words. An email to info@tecknika.net is enough to start.

02
Write the use case

We write it with you, and change it until it describes the job. Scope is agreed on paper.

03
Quote the build

The quote is made against the written use case, so both sides know what it covers.

04
Build

One engineer deep on every build — the people who wrote the use case write the software.

05
Hand over

Documentation and a deployment package, installed on a machine you control. Something you can keep.

Services

Seven services, one way of working.

Where every engagement starts

Requirements to use cases

Scope agreed on paper before a line of code — or a wire — is committed.
  • Your problem, written down. We turn what you need into written use cases: who does what, what the system answers, what happens when it goes wrong.
  • One document to agree on. You read it, we change it until it describes the job — and the quote is made against it.
  • Nothing templated. The use case decides what gets built, not a package we already have.

You get

Written use casesAgreed scopeA quote against it
Built to the written spec

Custom software development

Web applications, REST APIs and desktop clients.
  • The whole stack, one engineer deep. Back end, web front end and desktop client written by the same people, so the pieces fit.
  • Built to be kept. Delivered with documentation and a deployment package, installed on a machine you control.
  • The same way we build our own products. OSGA — web app, API and desktop companion — is built on this stack.

Stack

Java · Spring BootReact · TypeScriptJavaFXDocker
Into what you already use

Integrations

Connecting your software to the services your office already runs on.
  • Mail and calendars. Sending and reading mail through Microsoft 365, Google Workspace or a plain SMTP/IMAP mailbox, with calendar invitations people can answer.
  • Online meetings. Microsoft Teams, Zoom and Google Meet meetings created from your own system, with the link where people need it.
  • Files where they belong. S3-compatible storage and network shares for files, backups and archives — so nothing has to be typed in twice.

Connects to

Microsoft 365Google WorkspaceTeams · Zoom · MeetSMTP · IMAPS3 · network shares
The part the rest relies on

Databases & data models

Databases and table structures that back web applications.
  • Schema and relations designed from the use cases, so the data model matches how the office actually works.
  • Migrations that keep your data. Every change ships as a versioned migration, so an existing installation upgrades without losing a row.
  • Access patterns the front end relies on — searches, lists and reports that stay fast as the data grows.

Stack

PostgreSQLVersioned migrationsBackups built in
Keep what works

Legacy modernization

Bringing outdated codebases up to modern development standards.
  • Improve, don't discard. Functionality and performance are improved without throwing away what already works.
  • Written down first. What the old system does is captured as use cases before anything changes, so nothing is lost on the way.
  • Step by step. The system keeps running while it is brought up to date.

You get

A current codebaseDocumentationA deployment package
Ready to license

Software products

Finished tools you license per seat, supported by the people who wrote them.
  • OSGA — the project & document platform for engineering, architecture and licensing offices.
  • Gas Analyzer Logger — a live web view of a gas analyzer, with the readings collected as Excel.
  • Self-service. Installed on your own server, activated from the customer portal, no license key to paste.

Licensing

Per seatSelf-hostedPortal activation
View products →
When the job needs hardware

Custom engineering

Prototype machines from the electronics up.
  • Electronics and firmware. The working prototype built from the electronics up, with embedded firmware driving motors, valves and sensors.
  • Touchscreen HMIs on the machine itself, so the operator runs it without a PC.

Built with

Arduino C++TFT touchscreens
See the prototypes →

Have a project, or a case for us?

Tell us the problem and the constraints. We write the use case with you, quote the build, and ship something you can keep.

info@tecknika.net →