Applied IT research · Kraków, Poland
Institute
Registered in Kraków
Applied IT research for Poland's enterprise market
Focus
Technology analysis, applied research programs and compliance-focused guidance for teams that build, buy or govern enterprise IT.
Program state
1234567
Registry
KRS 0000949885
How to read the research
- PROGRAM Standing research track
- BRIEFING Dated tool note
- NOTE Regulatory reading
What the institute does
We research how enterprise technology is actually adopted in Poland, not how it is marketed. That means studying platform engineering practice, AI adoption inside real delivery teams, and the regulatory context that shapes procurement.
Applied research here has a narrow meaning. We take a live technology question from the Polish market, look at the available evidence, and publish findings that a working team can use. We do not sell software or resell vendor services, which keeps the analysis independent of any platform's commercial interest.
The registered office sits at ul. Józefa Sarego 5 in Kraków, and the institute operates as a sp. z o.o. under KRS 0000949885.
-
How the work is used
Architects and engineering leads take a published method and apply it to an active delivery question.
-
What stays out
No software licences, no vendor commissions, no implementation contracts attached to a finding.
-
What a reader gets
The evidence behind a claim, the limits of that evidence, and the decision it supports.
-
Where it starts
Every track begins with a scoped question drawn from the Polish enterprise market.
Research programs
Our programs are organised by technology area rather than by industry. Each one has a defined scope, a publication cadence and a stated method. The topic lists below are the questions the research is trying to answer.
If you want the detail rather than the summary, start at the program pages. Each lists the topics in scope and the questions the research is trying to answer.
Technology briefings
Short, dated notes on tools and platforms that teams are actively evaluating. They are written for people who already know the category and want a clear read on where it stands.
Orchestration
Kubernetes as an enterprise layer
Container orchestration remains central to enterprise modernization in Poland. The note looks at how teams run the platform day to day: the operating model, the tooling around it, and what shows up after the initial migration.
Development
Coding assistants in delivery
Generative AI has moved from experiment to workflow in a lot of Polish delivery teams. The briefing covers where assistants such as GitHub Copilot fit, and how teams keep code review and quality control intact.
Collaboration
Teams in hybrid-work governance
Collaboration platforms sit inside a governance question, not beside it. The note covers how Microsoft Teams is governed once meeting, chat and file retention fall under the same policy as the rest of the stack.
No vendor pitch, no feature list copied from a product page.
Compliance and risk notes are written as background for decision-makers, not as legal advice.
Compliance and risk notes
Regulation has become a first-order technology concern in Poland. DORA has applied to financial entities since 17 January 2025, with Polish implementing legislation supporting it from 7 August 2025. That changes how banks and fintechs assess ICT third-party providers, and it pushes risk management requirements down into ordinary vendor contracts.
The notes cover this territory: what a rule requires, which teams it touches, and what it means for procurement and outsourcing decisions. The 2026 environment for Polish IT companies is shaped by two overlapping pressures — cybersecurity obligations and AI governance. NIS2 and the Polish cybersecurity law have changed what vendor contracts need to cover, and teams deploying AI models now have to think about governance before deployment rather than after.
That is why the institute treats regulatory literacy as part of technology research rather than a separate discipline.
What a note covers
-
The rule — what it requires and the date it started to apply.
-
The teams — who inside a bank, fintech or vendor has to act on it.
-
The contracts — what it changes in third-party and outsourcing agreements.
-
The limits — where the note stops and legal advice begins.
Who this is for
The primary audience is technical and operational leadership in Polish enterprises: CTOs, platform and infrastructure leads, security and compliance managers, and the procurement staff who sit between them. We also write for consulting and outsourcing firms that need a defensible view of the local market.
If you are evaluating a platform, preparing for a regulatory review, or trying to understand how Polish software teams are actually using AI tools, the material here is meant for that work.
Engineering leadership
Platform and infrastructure leads deciding what to run, and how to run it after the migration.
Risk and security
Compliance managers turning a regulatory shift into controls a delivery team can hold to.
Procurement
Staff assessing ICT third-party providers, renewal terms and outsourcing arrangements.
Consulting and outsourcing
Firms that need a view of the Polish market they can defend in front of a client.
Kraków and Warsaw in the picture
Poland's IT market concentrates heavily around Kraków and Warsaw, and both cities show up in our research because the talent and startup activity are there. Warsaw in particular is a major outsourcing and software development hub, and it is where a lot of the current AI and robotics activity is clustering.
Location matters for research too. Being based in Kraków keeps us close to a large engineering labour pool and to the companies that hire from it, which makes a market question easier to check against the teams actually working on it.
The registered office at ul. Józefa Sarego 5 is where the institute is administered. Enquiries, program work and editorial review all run from there.
How we work
Every published item goes through the same editorial process: a defined topic scope, source verification, and a review pass before release. The methodology page sets out how topics are selected and how sources are checked.
We state limits where they exist. If the evidence on a question is thin, the note says so rather than filling the gap with a confident guess.
Methodology and editorial standards- 1 Define the topic scope. A question is only worth publishing if the boundary of the question is clear before the reading starts.
- 2 Verify sources. Claims are traced back to documentation, regulation text or practice we can describe.
- 3 Review before release. A second pass checks the finding against the scope and removes anything the evidence will not carry.
- 4 State the limits. Where the evidence is thin, the published note says so.
Why independence matters here
A research institute that also sold implementation services would have a conflict of interest in every recommendation. We do not. The institute publishes analysis and runs research programs; it does not take vendor commissions or resell platforms.
That constraint shapes what we publish. It also means we will say when a widely promoted approach does not hold up in the Polish market context.
Readers can check the claim, the source and the stated limit without asking who paid for the conclusion.
Registered entity
INSART INSTITUTE OF ADVANCED RESEARCH AND TECHNOLOGIES SP. Z O.O.
KRS 0000949885
NIP 6762610622
REGON 521068374
AI adoption and platform work, in practice
AI in delivery
Generative AI has moved from experiment to workflow in a lot of Polish delivery teams. Models such as OpenAI GPT-4o show up in support, search, drafting, and coding tasks, and coding assistants like GitHub Copilot are now common in day-to-day development.
The interesting questions are no longer whether to use these tools. They are about where the tools help, where they introduce review burden or risk, and how teams keep quality control intact.
Platform engineering
Container orchestration and platform work remain central to enterprise modernization in Poland. Kubernetes is the dominant orchestration layer for containerized workloads, used for scaling, resilience, and deployment automation, and it appears in a large share of modernization programs.
Mature teams organise delivery and operations with tooling that has been stable for years. Atlassian Jira remains a standard for issue tracking and agile delivery, usually paired with development and support systems that feed into the same workflow — sprint planning, incident workflow, and the handoffs between delivery and operations.
Questions we get asked
Short answers to the things that come up most often in first contact with the institute.
What is INSART Institute of Advanced Research and Technologies?
It is a research organisation registered in Kraków, Poland, operating as a sp. z o.o. under KRS 0000949885 and NIP 6762610622. It publishes applied IT research, technology briefings, and compliance-focused notes for the Polish enterprise technology market.
Does the institute sell software or consulting services?
No. The institute publishes research and runs research programs. It does not resell vendor platforms or take commissions, which keeps the published analysis independent.
Which technology areas does the institute cover?
Cloud-native architecture and platform engineering, AI adoption and model governance, and technology resilience including ICT risk management. Briefings and compliance notes sit alongside those program areas.
How do I get in touch?
The contact page lists the institute's Kraków address, phone number, and email, and includes a form for research or collaboration enquiries.
Research enquiries
We take enquiries from organisations that want to discuss a research topic, propose a collaboration, or ask about a specific program. Tell us the topic and the question you are working on, and we will route it to the relevant program.
We read everything that comes in. Response depends on relevance to current program work, but you will get an answer either way.
Institute contact
- Address
- ul. Józefa Sarego 5, lok. 4, 31-047 Kraków, Poland
- Phone
- +19082975632
- [email protected]
- Office hours
- Monday to Friday, 9:00 AM – 6:00 PM
Where the institute sits
The registered office is in Kraków's Stare Miasto district, a short walk from the city's main transport links and within reach of the engineering teams the research is written for.