Show HN: Jevper – the Jev interface on top of any OpenAI-compatible model https://ift.tt/2bgyuHe

Show HN: Jevper – the Jev interface on top of any OpenAI-compatible model jevper is the Jev interface pointed at whatever model you already have. https://ift.tt/bKgyRLZ September 23, 2026 at 02:25AM

Show HN: RxFilm Studio–Create and edit your product videos with AI agent https://ift.tt/myvprtJ

Show HN: RxFilm Studio–Create and edit your product videos with AI agent Hi HN, I built RxFilm Studio, a video workspace that lets you create and revise videos with AI agent. The reason I started this project is simple: I’ve noticed that many independent developers and small teams want to create marketing videos for their product, but producing these videos requires a lot of time and effort — from editing and visual effects to voiceovers and subtitles. So I built Rxfilm Studio to simplify the entire video creation process. Start with an idea, a product website, images, or existing footage, and then generate a complete video with: - Story and structure - Editing and timeline - Visual and sound effects - Voiceovers, background music - Subtitles and translation Github: https://ift.tt/FdIUn5b Here's a demo marketing video created using RxFilm Studio: https://youtu.be/9_M15fRdZQE Welcome to try it out and I would love to hear your feedback! https://ift.tt/5Zcd2GU September 23, 2026 at 02:28AM

Show HN: Run Linux kernel drivers in userspace on Neptune OS, NT-like OS on seL4 https://ift.tt/odYGRq6

Show HN: Run Linux kernel drivers in userspace on Neptune OS, NT-like OS on seL4 For the past ten years I have been working on a side project which I have taken to call Neptune OS [1], named after the ill-fated Microsoft Windows codename. Neptune OS is a Windows NT-like operating system built on the seL4 microkernel. The project has reached a point where it can run non-trivial, unmodified or minimally modified Windows or Linux kernel drivers as native (ie. NOT in a VM), unprivileged userspace processes on seL4. For instance, here [2] is amdgpu and i915 (from the Linux kernel DRM subsystem) successfully performing mode-setting on Haswell+Radeon RX560 for hotplugged monitors. The linked youtube channel has more demos for storage, networking, and power management drivers. Why I started working on this and why I think it is interesting: If you were familiar with early Windows NT development history, you'd probably know that NT was (allegedly) supposed to be a microkernel OS, where system services exist as user-mode servers sitting on top of a Mach-style port-based IPC. Unfortunately the late 1980s' computing technology prevented Microsoft from realizing this vision, and as a result the Windows we see today has everything dumped into kernel space (they even put an HTTP server in kernel mode!), leading to stability and security issues. This unrealized potential of the NT architecture never sat right to me, so when the seL4 microkernel was open-sourced back in 2014, I immediately thought, well perhaps one could rewrite NT as a personality on top of seL4. This "re-imagined" NT on seL4 will have the NT system call services implemented as a userspace process that talks to client processes via the high performance, formally verified seL4 IPC. Device drivers will then also run in isolated, unprivileged user processes, the crash of which will not lead to a BSOD-inducing full system crash. Another feature of the NT architecture I find very interesting is its so-called Environment Subsystems. These sit on top of the NT native system call services and expose them as more friendly user-facing APIs, such as Win32 and POSIX. I always thought it was a real shame that Microsoft has essentially given up on this idea and today's Windows is Win32-only (WSL1 being a much-needed redemption, but was then mercilessly dropped). With this seL4 rewrite of NT, I thought I could take this idea one step further and expand these environment subsystems to include device drivers, as they now run in userspace where they should have belonged. The result is the Linux Driver Subsystem in the latest v0.4 release of the project. In addition to native Windows drivers (which now run in userspace), this subsystem allows unmodified (or very minimally modified) Linux kernel drivers to run as native user processes on seL4. Note these are not virtual machines --- they are just regular, unprivileged processes. More technical details can be found in the mailing list announcement [3], but the basic idea is to add a new arch port to the Linux kernel similar to that of UML and the lkl (Linux-kernel-as-a-library) project. When compiled for this architecture, a reduced Linux kernel binary will essentially run as a regular program, requesting resources from the underlying host OS via the seL4 IPC. This binary communicates with the host OS via a carefully defined interface, which is in fact not tied to seL4 specifically, meaning our work can potentially be reused for other NT-like OSes (including Windows itself), or even other non NT-like OSes (with some more effort). Anyway, if you have read this far, I hope you find this project interesting. What do you think? What kind of applications do you think Neptune OS can potentially have? Do you think the project has sufficient industrial relevance to go beyond a hobby operating system? Let me know in the comments below. [1] https://ift.tt/Nwh23Un [2] https://youtu.be/BJIrUZIGgBc [3] https://ift.tt/WpuCLBR... September 23, 2026 at 12:02AM

Show HN: Drop – a rootless Linux sandbox with gVisor support https://ift.tt/sPxNAbC

Show HN: Drop – a rootless Linux sandbox with gVisor support I created Drop because I always felt uneasy installing and running third-party programs using my main user account. A single compromised dependency means a full compromise of the system. What is even worse, because I ship software from my computer, a single compromised dependency can lead to compromise of all the users of my software. Containers and VMs are one solution, but for local work, they are often detrimental to productivity. It takes effort to configure a machine with all the tools and configs needed for productive work, but a container or a VM will be stripped of all these tools. This is great for production deployments, where the aim is a reproducible system with minimal dependencies, but can get in the way of productive local work. Drop is language independent, but the workflow is inspired by Python's virtualenv. With virtualenv the environment isolation is only a convention that relies on installed dependencies being good citizens. With Drop the isolation is enforced. Each Drop environment gets its own writable and easily disposable home dir, with only selected config files and dirs from the original home mounted, mostly read-only. Drop uses Linux namespaces for isolation (user, mount, network, PID, IPC, cgroup), doesn't require root and, as an option, uses gVisor user-space kernel, which adds protection against exploiting host kernel vulnerabilities to escape the sandbox. I don't want to make the introductory post too lengthy, but I'm here to answer any questions and give any additional technical details. Note: This is my 3rd submission of the project, the first two did not draw attention. Since then I have added support for gVisor and created a project website to better explain the concept and organize documentation. https://droprun.sh/ September 22, 2026 at 03:52AM

Show HN: Watch all the AI agents on your machine https://ift.tt/T6GStzX

Show HN: Watch all the AI agents on your machine https://ift.tt/hSyG4pj September 22, 2026 at 12:57AM

Show HN: An atlas of system designs with interactive architecture diagrams https://ift.tt/3nksNow

Show HN: An atlas of system designs with interactive architecture diagrams https://atlas-sysdes.vercel.app/ September 22, 2026 at 12:54AM

Show HN: Lossless-memory – a personal AI memory that never summarizes https://ift.tt/G8HchOX

Show HN: Lossless-memory – a personal AI memory that never summarizes https://ift.tt/0RqIM6x September 21, 2026 at 02:28AM