Oh, I Found a Security Issue
Published October 26, 2026
This video features Georgios Poulos at DjangoCon Europe 2026 in Athens, Greece.
TALK: ATLAS: Building a Zero‑Budget IT Service Management Platform with Django in the Public Sector by Georgios Poulos
This talk presents ATLAS, a real-world Django application built and operated in the public sector under strict governance, security, and resource constraints. The session starts by outlining the organizational challenges of handling IT service requests at scale and why traditional email-based workflows failed. It then dives into the system’s architecture, focusing on workflow-driven design, authentication and authorization strategies, automation with SLA tracking, and observability through metrics and dashboards. The SLA model does not only enforce operational discipline but is also aligned with the organization’s official performance objectives, enabling IT teams to track compliance against organizational targets and support data-driven decision-making.
More information: https://2026.djangocon.eu/speakers/3EUCPF/
Follow DjangoCon Europe on social media:
*X - https://x.com/DjangoConEurope/
*LinkedIn - https://www.linkedin.com/company/djangocon-europe/
*Mastodon - https://fosstodon.org/@djangoconeurope
#django #djangocon #djangoconeurope #djangocon2026
Automatically transcribed, so expect mistakes in names and technical terms.
Speaker 1: Hello everyone and uh welcome back to the afternoon sessions. So uh for the next session we're going to have a very interesting and nice uh case study from the Greek government. Uh we're going to have uh George Poulos, uh who's working with the Ministry of Immigration. and he's going to share how they created the zero budget or very small budget application based on Zhang of course. That's being used now in the ministry. So thank you very much, George, and uh welcome to the conference.
Speaker 2: Welcome I work as a developer, as Adonis said, and system designer in the Greek public sector. Over the years I have built several applications with Django in Django, a framework that I love it because it keeps inspiring me to think clearly about architecture, workflows and real-world systems This is a real production story. How we built a serious internal IT service platform using Django under strict constraints. and with zero external budget.
Speaker 2: This talk is less about the features, but is more about workflows, architecture, and trust. So, internal platforms don't fail because of technology They fail because workflows are unclear and the system cannot explain what is happening. In this talk, I will show
Speaker 2: how replaced email driver coordination with explicit state-driven workflows, how meaningful metrics enforced emerged from the design and White Dango proved to be a great fit for building internal systems that needs clarity, reability, and long-term mentability Our starting point was typical, all we know it. IT support handled through emails, phone calls
Speaker 2: or informal conversations. Nothing was malicious, but everything was fragile. There was no clear ownership, no visibility, and no way to improve Because nothing was measurable. Atlas start an attempt to turn communication into explicit structured workflow
Speaker 2: So, what was the problem? Emails feels simple, but it scales ambiguity. In our case, we are supporting over two and a half thousand employees with a relatively small IT team, about 30 or 40 people. Agents, handling requests that span of dozens of different system and service categories For example, identify and access manager, office tools, internal business application VPN and internal access
Speaker 2: or external access, hardware, network services, security-based workflows. Each category has different DSLAs. and often different priorities and many times a lot of teams get involved. So as volume grows, you lose the signal. What's urgent? who owns what and what's actually happening. At that scale, emails stop being a tool and it becomes a liability.
Speaker 2: So the real Dhammad wasn't the slower responses time. It was the loss of trust. Users didn't know if their issue was mishandled. IT team could not explain the priorities. Management had zero visibility. Without visibility, you can't improve. You can only react Atlas is a workflow-driven IT service platform, not
Speaker 2: just a ticketing tool, not just a collection of forms. Everything is around state, is around ownership and responsibility All IT service requests go through a single and structured workflow. Roles are explicit. Permissions are enforced. Django works well in this space. because it encourages to model the real domain.
Speaker 2: States, transitions and permissions are part of the core system. not stated across scripts or configurations, with Django Admin acting as a control plane you could uh we could adapt workflows without constantly rewriting the application We intention we kept the user side extremely simple. Fewer choices, fewer mistakes, fewer mistakes, and of course fewer follow-ups. questions.
Speaker 2: Predictability matters more than clever UX in internal systems Users create a request in a minute. Not through emails, no follow-ups. Ownership is a part of the workflow. Agents can self-assign tickets and supervisors can assign responsibility where needed. The system makes responsibility explicit. The users can always know what happened next
Speaker 2: Okay, now let's switch perspective perspective from users to agents. Here is where architecture really starts to matter Tickets in Atlas are not just records. They are state machines. Every state transition happens for a reason and by someone with the right permissions. For example, a ticket may move from new to assigned to in progress or waiting
Speaker 2: and resolved With SLA starting, pausing, or stopping based on the state SLA timers are tied to state, not reports. Here, accountability becomes mechanical, not cultural. Let's zoom out and look at the system as a whole. This is the core architectural idea.
Speaker 2: Django is not just serving pages. It sucks like a workflow engine. States living models Policy Living Permissions Business rules live next to the data they protect. Email becomes an interface, not a system. Metrics emerge naturally from the workflow Atlas didn't end up being a single application.
Speaker 2: And one parenthesis. Over the time we built and integrated a few smaller Django tools that solved focused problems, some small, some not. And they operate together as a coherent system. What mattered was not uniformity, but shared principles Explicit workflow, shared identity, and predictable behavior The results now. This system runs in daily production. It's not a demo. It's not a pilot.
Speaker 2: We saw faster responses initiation, extremely high completion rates, and most important We restore trust. What mattered wasn't the speed. It was confidence and transparency. So, internal platforms live or die by workflow design. Djanco is
Speaker 2: exceptionally well suited for serious internal system where trust and governance matter. So what lessons learned, and what are the best practices for me? Model workflow first. Treat Django Admin as a control plane, not a back office Design from transparency. And Lin into Walt Django gives you for free.
Speaker 2: explicit models, clear permissions, and a framework that stays predictable even as system and organization change. After building and running multiple Django systems In production, it was consistently work for me and how I learned to build serious internal platforms Django doesn't scale the application only. Django scales trust between people
Speaker 2: and systems. Thank you.
Speaker 1: Thank you very much, George. So we have some time for questions if anybody has uh questions to share. I have one here. Oh, sorry. Coming there.
Speaker 3: Thank you for the interesting talk. I would like to know a bit more about the uh people behind it. So how easy was it for you to introduce the system? Did you meet resistance because people wanted to Cling on to the old broken process or um whom did you convince to be allowed to build this system?
Speaker 2: Uh if I understand your question, uh I work uh as a developer and system designer, I said before. But I get a lot of help with for my colleagues. Everyone could explain me and make to create a workflow about any job of any department of the ministry. So every time we we get another information to create the the right workflow. This I show is uh Our colleagues were very happy about
Speaker 2: this. They gave extra time to help us to design this. And then to test it and it this is was very uh important to test it. Thank you.
Speaker 1: I'm sure that the Greek public sector is very eager to try new stuff.
Speaker 2: Yes, it's another qua conversation.
Speaker 4: So you said that the uh state of each ticket is determined by a state machine and that you are able to change the behavior through the Django admin. Could you elaborate a little bit on how that state machine is changed and how you execute that one and store state resulting from that?
Speaker 2: Yes. So it's uh sometimes is från some states to another is automatic. In some other states are not so automatic and user need to change. For exαpl If one person gives the tickets to another, the state change automatic. If an agent closed the ticket and said we are okay , so he needs to change the status to resolve it. And uh we try to to keep it simple. Uh one uh one action
Speaker 2: and uh to do to do more things. It has a lot of signals behind, but I don't want to talk about features. It has a lot of features, Django features, the fantastic Django features. So we can uh we try to keep it simple and uh every everything human wants to do uh very simple the other is the the logic and the workflows uh Okay.
Speaker 1: Do you have more questions? Yep.
Speaker 5: Can I ask what the what what the zero budget is
Speaker 2: what is the zero budget?
Speaker 5: Yeah how how is this zero budget
Speaker 2: Yes. Okay. You will learn the more. Okay, I work as uh uh as an external partner for uh first for UNICR and after because I work in the migration first in uh uh the unit CR and after in the European Asylum service. So when I deployed at the ministry, the ministry has no budget to do some critical tools because and I come there, I uh I go there and I said to you okay this is We cannot fix it. We cannot react here.
Speaker 2: We cannot improve the situation. So there is Django. We can Django and me So we can do better things. This is the external budget because in the Greek public sector the budgets are uh is a constraint
Speaker 1: We also learned internals about uh the Greek budgeting system for the public sector. Other questions? We have I think uh time for maybe one or two more. Yep, I see one hand.
Speaker 6: Hello. Uh I'm curious how long did it take to actually implemented so from the idea to actual deployment how long did it take?
Speaker 2: Okay. Nice question This is not uh I give the system and this is the time. We design it about two or three months Uh we deploy we uh we do the application next two or three months but every time some someone else another department wants me okay we need to change this because we haven't uh this uh we want to do in this actions And uh I think six months was the core uh the core system
Speaker 2: and uh uh other uh the the the next time comes with uh some additions on the system Because it's not only the ticketing system. We have the warehouse of the ministry inside. We have some network uh mapping we have uh all the uh all the departments uh there And one one other that I want to, it was very helpful for us, was the the integration with Microsoft with Office. uh in the sign-in because we don't need to create new users
Speaker 2: but we we do the SSA with uh SS authentication With their uh accounts. So we don't need every time to create new users. Everything was ready and we just just give the right permissions. This is very helpful and uh the the work the colleagues there uh don't need to know a new code, a new password. They just sign in with SSO.
Speaker 1: Very helpful. Last week one. Cool Uh so I think this is it. George, thank you very much for this presentation.
April 15 - 17, 2026
Athens, Greece
Note: We understand that names change, people change, and bodies change. We respect each individual's journey and privacy. If you have any concerns about a video or need us to remove content, please don't hesitate to contact us. We will handle your request with care and promptly address any issues.
Published October 26, 2026
Published October 26, 2026
Published October 26, 2026
Published October 26, 2026
Published October 26, 2026
Published October 26, 2026