Software engineering since the 1990s
We connect systems. We build platforms. We sweat the details.
Proinet is a team of software engineers. We integrate applications and business processes, build SaaS and mobile platforms, and run the infrastructure underneath — from bare-metal Kubernetes clusters to mail and DNS.
- 1Existing system
- 2Integration layer
- 3New service
01Services
From integration to production
Eight areas where we have real production experience — not just a list of skills.
System integration and BPM processes
We connect CRM, ERP, accounting, payments and SaaS platforms, and move long-running business processes into a BPM engine — without rebuilding the systems that already work.
Details
DevOps and Kubernetes platforms
We build and run Kubernetes clusters on our own hardware, CI/CD pipelines and environments from test to canary. From compiling on the server to deployments in minutes.
Details
Web, SaaS and mobile applications
We design and build SaaS platforms, customer portals and admin panels, as well as iOS and Android apps — from architecture to app-store release.
Details
Websites and e-commerce
Company websites on modern CMS platforms, online stores and their migrations. SEO and analytics are a standard part of every project, not a separate engagement.
Details
AI in products and in software delivery
We build language models into products where they add real value, and work with AI agents every day — so code is better tested and documented, not just written faster.
Details
Internet of Things
Collecting, transmitting and processing device data — from an electronics prototype to a backend that ingests data from thousands of sensors. With security designed in from the start.
Details
Hosting and systems administration
We run our own server infrastructure — websites, applications, mail and DNS for businesses. With monitoring, backups and people who know how every component works.
Details
Security and infrastructure audits
IT infrastructure audits with a concrete remediation plan, security reviews, incident response and system hardening. A report you can act on, not one that sits on a shelf.
Details
02Case studies
Numbers, not promises
Selected projects. Descriptions are anonymised; the numbers, technologies and timelines are real.
- Industry
- SaaS platform, automotive (US market)
- Timeline
- 9 days
- from first code to production
- 4 days
- full UI integration
- 9 days
A BPM engine embedded in an existing CRM — in 9 days
Long-running customer processes — activating new accounts, reacting to declining activity, collecting confirmations — moved from spreadsheets and sales reps' memory into a BPM engine. Without rebuilding the admin panel the team already worked in.
Read the case study
- Industry
- SaaS — automotive intelligence (US)
- environments — test, beta, canary, production
- 4
- automated tests in the modernised service
- 0 → 200+
Modernising a SaaS platform — from a decade-old application server to full DevOps
An automotive data platform for the US market ran on an application server more than a decade old and was built by hand. We moved it to a modern stack, built new interfaces for customers and staff, and a complete CI/CD process on our own Kubernetes cluster.
Read the case study
- Industry
- Own product — mobile app for sailors
- Timeline
- 2 months (May–Jun 2026)
- platforms from one codebase
- 2
- languages
- 7
Sea Spotter — a mobile app for reporting marine wildlife sightings
Our own product. Sailors report marine wildlife sightings — dolphins, whales, orcas and more — and the app turns them into an activity map and alerts others nearby. iOS and Android, multiple languages, subscriptions, AI-powered species-name translation.
Read the case study
03Insights
Insights from projects
We write about what worked in practice — and about what did not.
2026-10-18
BiLSTM with attention on market data. The hard part is an honest experiment, not the network
Over several months we built BiLSTM networks with attention, a reinforcement-learning environment and a point-in-time fundamentals layer. What paid off most were not the architectures but placebos, thresholds fixed in advance and written-up negative results.
2026-10-18
Kubernetes is not just a new way to deploy. It changes your operational habits
Moving applications from servers into containers is the smaller part of the job. The bigger part is dropping old habits — host monitoring, logs in /var/log, the assumption that the application runs as a single instance, and knowing which machine it runs on.
2026-10-14
The customer as a process participant — BPM tasks from an email link
Some process steps can only be completed by the customer — confirm, accept, reply. Here is how to bring the customer into a BPM process without exposing the process engine and without tokens in links.
2026-10-10
AI does not ruin code. In an architect's hands it raises quality
The market consensus says language models flood repositories with lower-quality code. Our experience modernising a large platform is the opposite — on one condition.
Have a system that needs to talk to another system?
Describe the problem in a few sentences. We will reply with a concrete assessment of scope, risks and timeline.