Today, I visited a judicial services office in Iran for a work-related meeting. I went there to talk about work, but I ended up learning something interesting about the country’s digital infrastructure.
Just like the banking system, the judicial system uses a separate network. Employees need a VPN to connect to it instead of accessing everything through the regular internet.
At first, this makes sense. Judicial systems deal with sensitive information, and you probably don’t want random people on the internet accessing court records.
But the more I thought about it, the more questions I had.
What software are they running? How old is the infrastructure? How much of it could be improved with modern, free and open-source tools?
And, more importantly, could this become an opportunity to do something useful?
The Problem with Old Infrastructure
From what I saw, the systems in use seem seriously outdated. I haven’t inspected the actual infrastructure yet, so I can’t make claims about its exact age or security. But I can already see opportunities to explore better solutions.
Keeping a network separate from the public internet is not a bad idea by itself. In fact, systems handling legal records should have strict security controls.
However, isolation alone doesn’t make a system secure. Software still needs updates, access must be controlled, and administrators need tools they can maintain properly.
Old infrastructure can also make everyday work unnecessarily difficult. When systems are hard to maintain, depend on outdated software, or lack modern features, employees end up working around the technology instead of benefiting from it.
And this is where I think free software could help.
What Could We Replace with Free Software?
I’m interested in exploring whether some parts of this infrastructure could be modernized using free and open-source software.
I’m not talking about replacing the entire judicial system overnight. That would be expensive, risky, and probably a terrible idea.
Instead, I’d like to start with less sensitive services.
Think about internal communication, meetings, team collaboration, scheduling, and sharing non-sensitive documents between employees, judges, prosecutors, and lawyers.
Many organizations rely on proprietary platforms for these basic tasks, even when open alternatives already exist.
For example, Matrix could provide a foundation for internal messaging. Other open-source tools could handle collaboration, meetings, or document sharing.
Federation is especially interesting here.
Instead of forcing everyone to use one central platform, different departments or organizations could operate their own servers and communicate through shared protocols when appropriate.
This could give organizations more control over their infrastructure, reduce dependence on individual vendors, and make future migrations easier.
Of course, federation doesn’t mean connecting every system to the public internet. Sensitive legal records and critical systems would need separate security controls. Any deployment would have to be designed around the actual risks, not just the excitement of using new technology.
The goal is simple: use the right tool for the job, and avoid reinventing things that already work.
There is one challenge that could easily ruin an otherwise good project: Persian support.
And no, translating the interface is not enough.
A tool needs proper right-to-left support, correct text direction, usable Persian dates and calendars, reliable search, and layouts that handle Persian and English text together.
Anyone who has used poorly translated software knows the pain. Sometimes a button is in Persian, the error message is in English, and the text layout looks like it lost a fight with the browser.
That might be acceptable for a personal experiment. It is not acceptable for software used in legal work.
My preference is to take existing free-software projects and improve them instead of building everything from scratch.
If a good project needs better Persian support, we can work on the translation, fix the interface, improve the documentation, and contribute the changes upstream.
That way, the work can benefit other Persian-speaking users too.
I want to build something maintainable, not create another piece of software that only one person knows how to fix.
A Personal Complication
There is one slightly awkward detail about this potential project.
I have been detained for political reasons myself. I did not commit a crime. I exercised my right to freedom of expression, a basic human right.
Because of that experience, I obviously have complicated feelings about working with the judicial system.
But this is also a practical question. I need money to keep building Zist Digital, and a real infrastructure project could provide income while helping me develop something useful.
At the same time, I believe that building a free-software ecosystem in Iran requires us to work with organizations much larger than our own communities.
That includes universities, hospitals, industrial companies, banks, and government institutions.
Many of these organizations have outdated infrastructure and real operational problems. If we only work with people who already love Linux and open source, we will never reach much of the infrastructure that people depend on every day.
I don’t think working with an organization means agreeing with everything it does. But there are limits to the kind of work I am willing to accept, especially when technology could be used to make surveillance or political repression easier.
For me, the challenge is finding ways to improve the technology without ignoring the human consequences of how it is used.
A Small Note About My Detention
For context, my experience with the judicial system is not purely professional.
During my detention, I spent time in a small cell, roughly four by four metres, with a shower and toilet inside. The lights never went off. There was no window or clock, so I had to guess the time from the meals I received.
I was blindfolded whenever I was moved around the facility, and during interrogations, the interrogator sat behind me. I never saw the facility itself or even the staff working there.
My family was put under pressure and given false information. I also spent the entire detention dealing with nicotine withdrawal because I hadn’t written on my intake form that I smoked. Apparently, declaring it could have earned me a cigarette allowance. Great paperwork strategy on my part.
I managed to read two books, both religious, after repeatedly asking for something to read. I didn’t get to choose them.
It was a strange and difficult experience, and it is one reason this potential project feels different from an ordinary IT job.
I don’t want to turn this article into a story about my detention, but I also don’t want to pretend that my personal history has nothing to do with how I see this opportunity.
Why This Matters to Zist Digital
At Zist Digital, I care about digital continuity: building services that organizations can maintain and rely on even when the surrounding conditions are difficult.
Iran has plenty of reasons to care about that. Internet disruptions, access problems, changing service prices, and dependence on foreign platforms can all affect whether an organization can keep working.
Free software and open standards can help reduce those risks.
Organizations can inspect their software, maintain their own installations, adapt tools to their needs, and avoid being locked into a single vendor. Federated services can also give different teams more control over their own infrastructure.
None of this magically solves every problem. Open-source software still needs proper maintenance, security, backups, and people who know what they are doing.
But it gives organizations more options, and options matter.
I’d like to see these ideas become useful outside the small communities that already understand their value.
What Happens Next?
Right now, this is an idea, not a confirmed project.
I need to understand the existing systems, identify a practical starting point, and find out whether there is a genuine willingness to modernize anything.
The first step could be something relatively small: an internal communication service, a better collaboration tool, or improved Persian support for an existing open-source platform.
Any proposal would need to respect the security requirements of the institution, keep sensitive information properly protected, and avoid unsafe connections between isolated networks and external services.
It would also need a realistic budget and a maintenance plan. Installing software is the easy part. Keeping it running five years later is the real work.
I don’t know whether this opportunity will turn into anything. But it has made me think about what it actually takes to build a free-software ecosystem.
We need more than blog posts, Linux meetups, and arguments about which license is the most ethical.
We need working systems, real users, long-term maintenance, and organizations willing to try something different.
Sometimes, that means working with people who already share our values. Sometimes, it means approaching an organization we never expected to work with.
And sometimes, it means visiting a judicial office for a business meeting, discovering that its network runs separately from the internet, and leaving with a completely different set of questions.
Maybe nothing will come of it.
Or maybe the next step toward a stronger free-software ecosystem in Iran starts with something as simple as helping an organization use better software.
We’ll see.
Comments
There are currently no comments on this article.
Comment