Miloš Živković
Software & Cloud Engineerfounder & owner, ProtoCode
I work on secure, compliant and scalable systems, with twelve years of experience in software and cloud engineering. Today I work with SaaS companies, startups and enterprise clients that need scale and compliance.

- role
- Software & Cloud Engineer
- based in
- Zrenjanin, Serbia · remote only, mostly with international clients and open to clients anywhere
- company
- Founder and owner of ProtoCode, since January 2021
- experience
- 12 years
- works across
- Cloud infrastructure, platform engineering, DevOps, distributed systems, TypeScript, Node.js, AWS and AI implementation
- how I build
- Agents first, with tests, CI and my review on every change
- works with
- SaaS companies, startups and enterprise clients
What I work on
Most systems need all three areas at once: software that is built well, infrastructure that runs it at a sensible cost, and the security and compliance work around both. The fourth area is how I build all of it.
Software
Cloud
Security
Agents-first
Engineering log
Period, role, organisation, what I was responsible for, and the system it ran in.
open spanCurrent entries keep a line running off the page: the work is ongoing.
How I think about systems
Infrastructure decisions have business consequences.
Reliability requires explicit failure assumptions.
Security belongs in architecture and process, not in documentation alone.
Compliance controls should map to real systems and responsibilities.
How I build: agents first
Before an agent writes any code, I define the system it works in: the architecture, the conventions, the boundaries and the context it needs. The goal is a codebase an agent can understand before a person has to read it.
- Context firstarchitecture, conventions, context files
- Parallel agentsseparate, well-scoped tasks
- Tests & CItests, type checks, linters
- My reviewevery change
- Shipped
That is how I ship much faster than a conventional workflow. The speed comes from the engineering around the agents, not from skipping it: nothing an agent writes reaches production until it has passed the tests and CI and I have reviewed it.
Compliance readiness as engineering work
A compliance control eventually has to exist in an architecture, an infrastructure and an operating process. That is why I treat compliance readiness as engineering work.
On the SaaS platform where I am Technical Lead, I am taking the platform through readiness aligned with ISO/IEC 27001: security policies, system and architecture documentation, and the technical controls in AWS and the back-end services.readiness, not audit or certification
Miloš and ProtoCode
Related, not interchangeable. This site is about me; ProtoCode is the studio through which all my client work runs.
Miloš Živković
Software & Cloud Engineer
- role
- Founder and owner
- offers
- Development, architecture and implementation; consultancy for teams that need to implement AI or get ready for a compliance audit
- this site
- Who I am and what I can do
ProtoCode
Studio · services and projects
- what it is
- A studio providing software development, cloud architecture, DevOps, DevSecOps, compliance readiness, FinOps and AI implementation, usually for startups, SaaS platforms and enterprises
- client work
- All of it is contracted and invoiced through ProtoCode
- team
- Miloš, with sub-contractors when a project needs them
- website
- protocode.rs ↗
Where to verify
Each line points to something you can check. No badges, no logos.