Inspiration
The idea behind VEILOS came from a simple question: What if we could use applications without worrying about what they might leave behind on our systems?
Whenever we install or run unfamiliar software, we take certain risks with our files, privacy, and system resources. We wanted to explore a different approach where applications run in isolated, temporary environments and can be removed along with their workspace when we're done. This led us to build VEILOS, guided by one philosophy: Applications should be guests, not owners.
What it does
VEILOS is a privacy-focused, disposable computing operating system designed to give users greater control over how applications interact with their systems. It provides isolated workspaces for running applications, testing software, browsing, and development tasks.
Its core workflow is simple: Create, Configure, Use, and Destroy. Users can create a workspace, apply isolation policies, perform their tasks, and clean up the environment afterward. Features such as application sandboxing, temporary workspaces, a Privacy Center, and a planned custom privacy-focused browser are intended to make safer computing easier and more accessible.
How we built it
We built VEILOS on Debian 12, using Linux's existing security and isolation capabilities as the foundation. Technologies such as Bubblewrap, Linux namespaces, temporary filesystems (tmpfs), Bash scripting, and JSON-based profiles form the basis of our approach.
We also worked on building a live ISO so that VEILOS could be booted and tested in a separate environment. Tools such as live-build, xorriso, and QEMU support the operating system build and testing workflow. Our focus was not just to create another Linux distribution, but to develop a system where application isolation and workspace cleanup are central to the user experience.
Challenges we ran into
One of our biggest challenges was understanding the difference between simply closing an application and properly cleaning up its environment. A workspace needs to manage running processes, temporary files, filesystem access, and network permissions carefully.
We also had to think beyond the interface and consider what happens when an application crashes, a session ends unexpectedly, or a cleanup operation fails. Another challenge was balancing usability with security, because stronger restrictions can sometimes interfere with normal application behaviour. These challenges helped us understand that privacy is not just about adding features; it requires careful implementation and testing.
Accomplishments that we're proud of
We're proud to have developed the foundation of VEILOS as a live operating system focused on disposable computing. Bringing together Linux isolation technologies, workspace management, and an automated ISO build workflow was an important step in turning our idea into a working project.
We're also proud of the concept behind VEILOS: making application isolation a part of the overall computing experience instead of expecting every user to configure separate security tools. The project has given us a foundation that we can continue improving through better isolation, clearer security reporting, and a more user-friendly interface.
What we learned
While building VEILOS, we learned that creating a secure computing environment involves much more than writing code or designing an interface. We explored Linux namespaces, sandboxing, temporary storage, process management, live operating system builds, and automated testing.
We also learned to distinguish between a security feature and a verified security guarantee. A temporary filesystem, for example, can help manage disposable data, but it does not automatically guarantee complete forensic erasure. This experience taught us to test our assumptions, understand our limitations, and build security features with transparency in mind.
What's next for VEILOS – Disposable Computing Operating System
Our next goal is to make VEILOS more practical, reliable, and accessible. We plan to improve workspace lifecycle management, strengthen filesystem and network isolation, and make the Privacy Center reflect the actual security state of running applications.
We also aim to develop our own VEIL Browser experience, featuring disposable browsing sessions and privacy controls, while being transparent about the underlying browser engine. Other areas of improvement include stronger display isolation, more granular permissions, better crash recovery, and expanded automated security testing.
Our long-term vision is to make disposable computing useful for students, developers, researchers, and privacy-conscious users. We want people to focus on what they need to do, while VEILOS helps them keep their digital workspace more controlled and temporary.
VEILOS — Run Apps. Not Risks.
Log in or sign up for Devpost to join the conversation.