Your prototype needs to become a product.
- Your software is slow and nobody dares touch it.
- Your organization runs on spreadsheets.
- Your big technical decision has no second opinion.
- Your website can’t be changed without a developer.
We can help with that.
A small senior practice, a handful of clients at a time, working remotely with clients anywhere. Tell us what you are trying to get done, and we will say whether it is something we take on.
Thanks. Your note is with us.
We will reply by email. If it is something we can help with, the next step is a short call.
Or write to hello@maybloom.tech, or book a call.
Tell us what you’re trying to do.
Where things stand today, and what you would like to be true instead. A sentence or two is enough.
What people come to us with.
Whether you are one person, a small team, a cooperative, or a nonprofit, one of them is probably yours.
-
Your prototype needs to become a product.
Tell us about this: A prototype that shipsWe take what you have built, find what stops it holding up with real users, and get it live. You end up with something running for real that you or your team can keep changing.
What you get
- A plan for what stands between the prototype and launch.
- The remaining work, built and taken from plan to launch.
- The servers and services it runs on, set up so it stays up.
-
Your software is slow and nobody dares touch it.
Tell us about this: Software that is safe to changeWe find where the time goes and what makes changes risky, then fix the worst of it a step at a time. You end up with software your people can change without fear.
What you get
- A review of how the system is put together and where it breaks.
- Slowness and outages tracked down and fixed.
- A short list of what to fix first, and the fixes.
-
Your organization runs on spreadsheets.
Tell us about this: One place for your dataFor a business, a nonprofit, or a cooperative, we replace the spreadsheet with software shaped to how you work, including in the field with no signal. You end up with one place where the data lives.
What you get
- Software built around the way your people actually work.
- Field data collection that works without a signal and syncs when it can.
- A way to bring sensor, sampling, or monitoring readings together in one place.
Our incident system for Oregon Country Fair lets coordinators record what happened, who was involved, and what was done, where paper and group chats lose the thread. Read about the work.
-
Your big technical decision has no second opinion.
Tell us about this: A second opinionWe review the plan with you and say plainly what to build, what to buy, and what to skip. You end up with a decision you can defend.
What you get
- A review of the plan before you commit to it.
- A clear answer on what to build, what to buy, and what to skip.
- A design for how your software connects to other software, built to last for years.
- Help judging the engineers you are thinking of hiring.
-
Your website can’t be changed without a developer.
Tell us about this: A website you can changeFor a nonprofit, a small business, or an independent professional, we build a site that is cheap to run and easy to change. You end up with a site you are not locked into.
What you get
- A site for a nonprofit, a small business, or an independent professional.
- A landing page for a launch or a campaign.
- Built to stay cheap to run and easy to change.
-
Something else.
Tell us about this: something elseIf your problem isn’t on this list, that’s a fine reason to write.
Who does the work.
Miguel Cervera
Maybloom Tech is led by Miguel Cervera, a staff‑level engineer with thirteen years building internet‑scale systems: APIs, platforms, and the infrastructure underneath.
Built as an engineer at Twitter, Stripe, Uniswap Labs and Caldera, before founding the practice. US Patent 11,095,581.
The practice runs from a 10-acre permaculture homestead in the Willamette Valley.
Gardens, a food forest, bees, biochar, air-quality monitoring, and the software that keeps track of all of it. Miguel also serves as Vice President of the Board at Beyond Toxics, an Oregon environmental-justice nonprofit.
What you can check for yourself.
-
Incident Management SystemOregon Country Fair, 2026
Field incident logging for a large volunteer-run event, built so coordinators can record what happened, who was involved, and what was done.
Read about it -
The Maybloom Stackstack.maybloom.tech
The setup we use ourselves to build software with AI agents is open source: a project template, and agents that build and review the work in a loop.
See the setup
The tools and systems we work with
For the engineers on your side. A working stack, built on resilient and fault‑tolerant systems.
- Practice
- Staff‑level review · Architecture review · Hiring eval · Second opinion
- Languages
- TypeScript · Scala · Python · Go · Solidity · Ruby
- APIs
- Protobuf / Connect‑RPC · GraphQL · REST · Thrift
- Cloud & infra
- AWS · Terraform · Kubernetes · Postgres · NoSQL
- AI
- Claude / Anthropic SDK · Agentic tooling · Surrounding ecosystem
- Onchain
- EVM · Ethereum · Arbitrum · OP Stack · Solidity · Cross‑chain bridging
- Domains
- Offline‑first field data · Sensor & monitoring pipelines · Resilient & fault‑tolerant systems · Multi‑service architectures · API design · Backend frameworks · Data pipelines · Regulatory‑compliance APIs
Talk it through on a call.
A short call is all it takes to figure out whether we can help.
On that call we agree a scope and either a fixed price or a monthly arrangement, and begin.
Pick a time that works