What the name means
Jet + blip
JEremy Trindade. The founder's initials, hidden in plain sight as a real English word. To anyone outside the brand it reads as flight and speed, which is a happy feature for a tech umbrella. Inside, it is a personal signature that travels across every project under the roof. Carried over unchanged from the earlier AI Jet Labs era.
A blip is a single observable point, the radar-style burst of an event. Each project under the umbrella is one blip: small, observable, deployable. This is the deliberate shift from the earlier "Labs" framing (experiments cooking) to "blip" framing (signals deployed). The umbrella ships in blips, not in lab notebooks.
Naming pattern across the product layer: repos are blip-<function>, subdomains are <function>.jetblip.com, API endpoints are /api/blip-<function>/, systemd units are blip-<function>.service.
Evolution
A better way to communicate with USA universities
The work that became Jetblip started as a personal need, not a product. I needed a more proper way to handle communication with universities in the United States as part of my own studies, and the existing tools either did too little or too much. The first sketches were small scripts that solved one annoying piece of that workflow at a time.
Built and ran it on my own machine first
The first working version lived on my personal Windows PC. That was the right place to start: zero ops cost, fast iteration, no cloud bills while the idea was still finding its shape. The whole project ran as long as the PC was on.
If I leave the house, the project goes offline
Two things made the local-PC setup uncomfortable. First, I did not want to keep the PC running 24/7. Second, when I needed to travel, the project effectively went offline with me. The honest constraint was: this thing has to live somewhere that is not my laptop.
A Google Cloud VM as the first move off-PC
I tested my first VM on Google Cloud Platform. It worked. The project could now stay alive while I closed the laptop or boarded a flight. GCP became the v2 era for this whole personal-infra line, and several of the early subprojects were built and shipped on that VM.
Bringing in a Raspberry Pi for a more permanent home
Once the structure was more organized, I started looking at moving things to dedicated home hardware. A Raspberry Pi felt like the right size: real Linux, predictable cost, no cloud surprises, mine to run. The plan became: keep building on cloud, then migrate the whole thing to the Pi when the codebase was stable enough to survive the move.
Around 60 to 70 percent done, stop and organize before migrating
Before landing the project on the Pi, I deliberately paused on new features. I went through the whole stack and reorganized: standardized naming, consolidated repos, cleaned up the deploy story, made services restartable. Without that pause the migration would have inherited every piece of accidental complexity from the cloud setup.
From AI Jet Labs to Jetblip, one-word umbrella, real .com
The first umbrella was AI Jet Labs at aijetlabs.com. It served the v1 brand era through May 2026. A 50-candidate audit in 2026-05 found that jetblip.com was the strongest available one-word umbrella: a real English word as apex, the founder signature preserved in "Jet", and a cohesive child-naming pattern (every repo is blip-<function>). The earlier aijetlabs.com stays owned and 301-redirects here.
Running on a Raspberry Pi 5, 4 GB
Right now the umbrella lives on a Raspberry Pi 5 (4 GB RAM). Power-frugal, always on, fixed monthly cost. The cloud-era pieces are either fully migrated or in the process of being phased out. New blips start on the Pi from day one.
The story is not finished. As ideas get bigger, parts may move back to cloud, some may stay home, and the next generation may be a small home-server cluster. The point of Jetblip is to keep that journey legible.
Tech touched along the way
Projects under the umbrella
blip-web-jet
The Active Cortex landing: Bento Grids 2.0, Magic UI motion, brain-graph telemetry, terminal feed wired to the live rules folder.
github.com/jeremytrindade/blip-web-jet CREblip-web-trindade
The Cream Architecture identity: tactile paper textures, Instrument Serif headings, Trinity-orange accent, calm-as-craft motion.
github.com/jeremytrindade/blip-web-trindade CRTblip-web-trinity
The Phosphor Workshop: CRT-green scanlines, layered monospace stack, metric cards and sparklines, dark-cyber telemetry aesthetic.
github.com/jeremytrindade/blip-web-trinity UoPweekly-uopeople-setup
Self-running weekly study-guide pipeline for the operator's UoPeople coursework. Extract, generate, verify, audit, all on a Thursday cron.
github.com/jeremytrindade/weekly-uopeople-setup MIGlabs-migration-gcp-to-rpi
The migration story from the GCP VM era to the Raspberry Pi 5. Documents the decisions, pitfalls, and the recovery procedures.
github.com/jeremytrindade/labs-migration-gcp-to-rpi PI5rpi5-usages
What the Raspberry Pi 5 in this lab is doing right now. Resource accounting, capacity headroom, what next.
github.com/jeremytrindade/rpi5-usages