INSART
Applied IT research
Institute
INSART Institute of Advanced Research and Technologies
Scope
Five lines of work
Market
Poland, enterprise technology
Cadence
1234567
Notes and briefings through the week
The institute runs a small set of research programs, each covering a defined technology area and a defined set of questions. This page describes what each program covers, how topics are selected within it, and what the published output looks like.
State key
Five lines of work, each with a fixed scope and its own publishing rhythm. The day-code column shows how a programme currently runs.
Programme
Containerized and cloud-native systems in Polish enterprises: operating models, platform team structure, tooling around the orchestrator, and the trade-offs that surface after the first migration is finished.
1234567
Research notes
Enterprise platform teams
Programme
Where generative and multimodal models reduce effort in support, search, drafting and coding — and where they add review burden, quality questions and governance obligations before deployment.
1234567
Research notes
Delivery and support leads
Programme
The regulatory and operational side of resilience: ICT risk management requirements, third-party assessment, and the due-diligence expectations that procurement and outsourcing decisions now carry.
1234567
Research notes
Procurement and risk teams
Programme
How mature teams organise sprint planning, incident workflow and the handoffs between delivery and operations — the seams that break first when a team is under pressure.
1_3_5_7
Briefings
Engineering managers
Programme
Collaboration platforms as part of IT governance: how meetings, file sharing and cross-functional work shape operations in hybrid settings, and what storing corporate content in a daily-use platform means for control.
1234567
Research notes
IT operations and governance
The five programs share one editorial group and one review path. Each entry below describes the questions a program answers and the technology area it holds.
Programme one
This program covers how Polish enterprises build and operate containerized and cloud-native systems. Kubernetes sits at the centre of it: it is the dominant orchestration layer for containerized workloads, used for scaling, resilience, and deployment automation, and it appears in a large share of enterprise modernization programs.
The research here is not about whether to adopt Kubernetes. It is about the operating model around it: how platform teams are structured, what tooling sits alongside the orchestrator, and what trade-offs show up after the initial migration is done.
Inside the program, a topic is researched only when there is public evidence to work from. Cluster cost models, platform team size, the split between self-service and review gates, and the point at which an internal platform stops paying for itself are all in scope.
Questions the program holds
Programme two
The AI program looks at how generative and multimodal models are used inside delivery and support workflows. Models such as OpenAI GPT-4o appear in assistant-style and workflow-integrated roles, and coding assistants including GitHub Copilot are now common in day-to-day development.
Where effort drops
Support triage, internal search, first-draft writing and routine coding tasks are the areas where teams report the clearest reduction in manual work.
Where burden rises
Every generated answer still needs a reviewer. Review capacity, acceptance criteria and the record of who approved what become the real constraint.
What governance asks
Which data may reach a model, which decisions stay human, and what is documented before a tool goes live rather than after an incident.
What the notes cover
Rollout sequencing, pilot scope, the difference between assistant and workflow-integrated use, and the review steps each one implies.
AI adoption and model governance is between research cycles until the next note is released.
How topics are selectedProgramme three
This program covers the regulatory and operational side of technology resilience. DORA has applied to financial entities since 17 January 2025, with Polish implementing legislation supporting it from 7 August 2025. The rules raise requirements for ICT risk management and for how third-party providers are assessed.
That reaches well beyond financial services. Technology procurement and outsourcing decisions now carry due-diligence expectations that procurement teams have to meet, and the program's research is aimed at making those expectations legible.
Dates that matter
What procurement now has to answer
Programme four
A fourth line of work covers the tooling and process side of software delivery. Atlassian Jira remains a standard for issue tracking and agile delivery in Polish software and IT operations teams, usually connected to development and support systems that feed the same workflow.
What the research looks at
How mature teams organise delivery and operations: sprint planning, incident workflow, and the handoffs between delivery and operations that tend to break first under pressure.
Notes here are practical rather than theoretical — the pattern is described, then tested against how teams actually work.
Programme five
Collaboration platforms are now part of IT governance, not just productivity. Microsoft Teams is a mainstream enterprise platform, common wherever Microsoft 365 is standard, and it carries meetings, file sharing, and cross-functional work.
The program examines how collaboration tooling shapes IT operations in hybrid-work settings, including the governance questions that come with storing corporate content in a platform most staff use daily.
Topic selection starts from a question the Polish market is actually asking. A topic enters a program when there is enough public evidence to research it and a real audience that needs the answer.
Within a program, topics are sequenced so that published items build on each other rather than repeating. A topic that duplicates an earlier note is either folded into it or dropped.
A question arrives from the market, a reader, or a programme's own backlog.
The editorial group checks whether public evidence exists to research it properly.
The topic is assigned to the programme whose scope it fits, and sequenced against existing items.
Draft, review, and release — with the limits of the evidence stated in the note itself.
The methodology page describes the full selection and verification process.
Program output takes two forms: longer research notes tied to a program's core questions, and shorter briefings tied to current developments. Both go through the same review before release.
Research notes state the question, the evidence, and the limits of what the evidence supports. Where the picture is incomplete, the note says so.
Research notes
Longer pieces tied to a programme's core questions. They open with the question, set out the evidence, and close with what the evidence does and does not support.
Briefings
Shorter pieces tied to current developments. Useful when something changes and a reader needs the practical consequence rather than the full background.
Organisations can contact the institute about a specific program, propose a topic, or ask whether a question falls within a program's scope. The contact page has the details for written enquiries.
Enquiries are handled Monday to Friday, 9:00 AM – 6:00 PM. Written enquiries go to [email protected] or +19082975632. The institute is at ul. Józefa Sarego 5, lok. 4, 31-047 Kraków, Poland.
Contact the institute about a programYes. Topic proposals go to the editorial group that selects topics. A proposal is more likely to be taken up if it maps to an existing program scope and there is enough public evidence to research it.
The institute runs its own programs and publishes independently. Enquiries about collaboration are welcome, but commissioned work does not change how findings are published.
Platform running costs sit inside cloud-native architecture and platform engineering. Provider and contract cost sits inside technology resilience and ICT risk. If a question crosses both, the editorial group decides which programme publishes it and says so in the note.
Next step
Bring a question, or read what the programs have already published. Both routes are open to anyone working on enterprise technology in Poland.