Read the code, then decide.
You have a piece of software that keeps getting deferred because it needs a kernel API, a text engine or a real browser. I build that part, alone, remote from Israel.
Your desktop app eats a gigabyte to draw a menu
It is Electron because nobody on the team writes Swift, and your users feel it on battery. I write the small native thing instead: menu bar, straight to the system, no driver and no kext.
opendisplay 61 commits · trumpet 8 · Swift
The scraper worked until the site asked for a login
Headless browsers get flagged, blocked, or quietly served a different page. I build the extension and the bridge behind it, so your program drives the browser where the login already lives.
responsive-viewer · open-claude-in-chrome
Hebrew renders backwards inside your own product
The name reverses, the comma jumps to the wrong end, the niqqud lands on the neighbouring letter. Reordering, joining and mark placement are three problems, and most engines solve only the first.
termisu 433 commits · Rust core, Swift host
Nobody will let the agent near the real repo
The tool promises to ask before writing, then a tool inside it writes anyway. I measured it. So the wall belongs under the agent, in the kernel, where it cannot be consulted or edited.
januas 440 · claude-code 89762, 89165, 84863
- termisuA terminal written from zero433
- octootterDesktop app around the claude CLI190
- azakaRed Alert map for Israel75
- opendisplaymacOS display panel, no kext61
- glyphcastVideo as a grid of glyphs36
- sottoSpeak Hebrew, get clean text36
- wisp-adblock-testWhat your blocker actually catches23
- januas-adeGPU terminal multiplexer23
- trumpetPer app volume, CoreAudio taps8
- isqICQ rebuilt, agents as members6
- melA language in the enchanting alphabet6
- orellius-TCMTelegram OSINT with LangGraph6
- responsive-viewerAny device size, in place4
- yayinWindows games on a Mac2
All readable right now. None of it is a demo. github.com/Orellius
- Step 01You send the problem, not a specOne email with what breaks and what it blocks. If I cannot build it, I say so and point you somewhere better.
- Step 02A scope in writing, then a priceOne page: what ships, what does not, where the risk sits. The price comes with it, fixed for the whole piece.
- Step 03Something running, in week oneThe first thing I hand over runs on your machine. After that you read the repo and the failures as they land.
- Step 04Handover you can build onSource, build instructions and the reasons behind the awkward calls. No retainer and no runtime of mine.
Where it stands today
Open for the next project.
No clients yet, and you would be the first. Every project above is code you can read before you pay. Remote from Israel, English or Hebrew.