Built by Rainmaker
Rainmaker is the custom-build workshop behind Ryxen and a growing set of manufacturing tools, public data systems and operational resources. The point is not the number of projects. The point is that the same builder pitching your system already has to design, deploy, maintain and live with software of its own.
Products · public tools · scheduled systems · real production infrastructure
Rainmaker's strongest proof is not a gallery of screenshots. It is the collection of systems that must keep working after the screenshot is taken: authentication, databases, scheduled jobs, alerts, PDFs, search, data ingestion, backups, deployment and real users.
Ryxen · the product side
Ryxen is where recurring problems become products. These systems are deliberately narrow: fewer modules, less consulting, faster trial and clearer operational jobs.
Machine records, service history, parts and vendor context, maintenance workflows, QR access and quick logging built around the reality that work often gets done before anyone remembers to document it.
Focused compliance and safety workflows for small manufacturers: organized records, reporting, shareable output and a simpler path than forcing a small operation into a heavyweight EHS platform.
A focused materials/order workflow for cabinet, millwork and similar shops where Excel, email and memory often act as the purchasing/status system.
Not everything should become SaaS
Some problems deserve a product. Others deserve a data pipeline, monitor, calculator, internal utility or public research tool. The ability to stop before “platform” is part of the discipline.
A source-backed data pipeline that gathers, normalizes and publishes manufacturing investment and modernization records while preserving official-source links, review rules and last-known-good output.
Open the tracker →A structured content pipeline built to publish large manufacturing SOP libraries consistently without relying on free-form AI generation for every page.
Browse the SOP library →Small utilities for sheet weight, edgebanding, OTIF and other recurring calculations where a ten-second tool is more useful than another application.
Open the calculators →A large public reference layer around manufacturing, operations, maintenance and production terminology—designed as durable infrastructure rather than one-off blog content.
Browse the glossary →What the visible product does not show
Good software is more than its interface. Rainmaker's own systems have to deal with the unglamorous production concerns that client work eventually faces too.
User accounts, organization boundaries, permissions and protecting one customer's data from another.
Persistent records, searchable history, workflow state, exports and migrations instead of browser-only demos.
Tasks that keep running when nobody has the app open: checks, updates, watchdogs and exception detection.
Systems that surface the exception instead of depending on a manager remembering another dashboard.
Operational software has to leave the application cleanly when customers, auditors or outside users need the information.
Short paths from machine, asset or job to the exact screen needed in the moment.
Safe behaviour when APIs, source pages, networks or dependencies fail instead of publishing partial or corrupt state.
Software that has to run on real servers, survive updates and remain supportable after launch.
What that proves
The point of showing the underlying capabilities is not technical theatre. It is to demonstrate that Rainmaker repeatedly solves the same classes of production concerns a custom client eventually depends on.
Public work
Rainmaker and Ryxen publish useful manufacturing resources because domain understanding should be visible before a prospect has to trust a proposal.
Ungated manufacturing procedures across safety, maintenance, machines and quality.
Browse SOPs →A growing manufacturing and operations reference library.
Browse glossary →Focused manufacturing and business tools with no sign-up requirement.
Use calculators →Source-backed public research around investment and modernization activity.
Open tracker →The Rainmaker build standard
If “Built by Rainmaker” is going to become a maker mark, it has to represent a consistent operating standard—not merely who wrote the HTML or Python.
The exact stack can change. The operating expectations should not.
The category difference
The ambition is not to look bigger than Rainmaker is. It is to make the actual advantage legible: one operator-builder repeatedly solving narrow operating problems and carrying the lessons across products and client work.
Useful, but easy for almost any development studio to assemble.
Harder to manufacture because the systems have to continue existing.
The practical takeaway
You do not need to know whether the answer is a small automation, an internal application or something you should buy instead. The first job is to understand the workflow well enough to choose correctly.