Ruom Inc · 若木
Software for the moment someone has to go and look.
Ruom builds vertical SaaS for industries where the record and the fact are different things — verifying an address in Shenzhen, reading whether a resident will actually renew, putting a seat at a curb at 4 a.m. Three products, three industries, one job: turn a claim into something observed.
Hemisphere
Verifying the Eastern Hemisphere.
A U.S. firm has a defendant with a Chinese address on file. Hemisphere sends someone to that address and reports what is actually there — then delivers it as structured evidence, not a PDF in an email thread.
Address Verification Report
Registry research, mapping, address validation, and risk indicators on where a defendant is registered versus where it operates.
Onsite Verification Report
An investigator goes to the site. Photographs, signage, observed activity — what stands at that address today, not last filing.
Business information verification
Registration data, address consistency across filings, and online presence pulled into one record you can actually compare.
Structured reporting
Every report follows the same schema, so the tenth one reads like the first — and can be set beside it in a filing.
Client portal
Open a matter, upload a defendant list, track status per defendant. The status lives in one place instead of five inboxes.
Firm-level isolation
Records are scoped to your firm in the database itself, enforced by row-level security — not by a button we chose not to render.
Commons
Know who is leaving before they tell you.
A renewal survey asks a resident what they intend to do. Commons watches what they actually do — then scores it, shows its own calibration, and hands the community manager a ranked list for this week.
Renewal probability scoring
Every resident scored, with calibration curves and feature importance on the same screen. A score you cannot interrogate is a rumour.
Engagement time series
Participation tracked week over week, broken out by building and by engagement decile, so a dip has an address.
Ranked actions
The output is not a dashboard. It is an ordered list of what to do next, sorted by expected effect on renewals.
Quiet-resident detection
Surfaces residents who have gone silent — the earliest reliable signal that notice is coming, and the cheapest one to act on.
Polls and closed loops
Run amenity and priority polls, then show residents what changed because of them. The visible loop is the retention mechanism.
NOI attribution
Retention lift translated into portfolio dollars — with the counterfactual and the limits of the claim printed on the same page.
Lillian Wright
Shared airport rides, booked in about a minute.
On-demand apps promise a car and settle up afterward. Lillian Wright publishes the departure first — fixed fare, four to six seats, a held seat with your name on it before you close the tab.
Published departures
Operators publish real routes and times. A traveler picks an actual departure, not an estimated pickup window that moves.
Fixed fare, shown first
One-way or round trip, priced end to end before an account is required. No surge, no reconciliation after the fact.
Guest checkout
Book without signing up. Stripe handles payment — we do not manufacture an account in order to take someone's money.
Seat holds
A seat is reserved while the traveler pays, then released automatically. No double-sold rows on a van with six of them.
Stated luggage allowance
One large and one small bag each, plus a free carry-on. Written down, so the curb at 4 a.m. is not where it gets negotiated.
Operator console
Publish departures, manage bookings, and notify every affected passenger the moment a trip changes — before they leave home.
The tree at the western edge of the world. 其华照下地 — "its blossoms light the ground below." Not the sky. The ground, and the things standing on it.
The brand story →How we build
We are our own first customer
Each product began inside an operation we run ourselves. That is why the workflow fits — we found the gaps by standing in them, not by interviewing someone who had.
One stack, three products
Next.js, TypeScript, Supabase, Vercel — in all three. Changing context is not changing tooling, so a fix learned once applies everywhere.
Security at the data layer
Row-level security decides who sees what — not a hidden button, not a filtered query. Service-role credentials never reach a browser.
Phased, and written down
Every product ships in numbered phases against a roadmap that names what is explicitly out of scope. Ambiguity is the expensive part.
Get in touch
Talk to the people who run it.
A firm with a defendant in Guangdong, an owner with a renewal problem, a traveler with a 6 a.m. flight — whichever you are, you will be talking to someone who works on the product.