Who's Actually Behind Okidoky? (One Person, No VC)

On most finance apps the "About us" page looks the same: a photo of a smiling team of ten to fifty, a vague mission statement, and a list of investors you've never heard of. Who actually writes the code and who decides what happens to your data — that's almost never clear.

At Okidoky it's different. Not as a marketing choice, but because the reality is smaller than a glossy About page would suggest. Here's who is actually behind it.

One person. One sole proprietorship.

Okidoky is developed by RULIDO, a Dutch sole proprietorship (eenmanszaak) in the Netherlands, registered in 2024. The Chamber of Commerce registration is publicly verifiable under number 98709364. No private limited company, no holding structure, no parent in Ireland for tax purposes. One person responsible for:

  • The code (front- and backend)
  • Security
  • Email support
  • Decisions about features and about what won't be built
  • Accountability to the Dutch Data Protection Authority if an incident happens

On some axes that's a disadvantage. There's no 24/7 support team. Vacations mean slower email replies for a week. If the founder is ill, development pauses.

On other axes it's an advantage: every decision runs through one head. There's no investor pitching why the free tier needs to be trimmed to hit the next funding round. There's no board meeting where "monetisation" is on the agenda. If a feature doesn't fit "a simple household ledger", it just doesn't get built.

No outside investors

Okidoky is fully bootstrapped. That means: revenue comes from subscriptions (Premium, Lifetime, Duo, Family Lifetime) and limited, non-intrusive ads for free users. No VC round, no angels, no growth capital.

What that means in practice:

  1. No pressure to sell. VC-backed startups usually have to show an exit within 5-7 years (acquisition or IPO). That shapes every product decision. Okidoky has no such pressure.
  2. No data-monetisation incentive. Revenue via selling or renting user data is a typical VC exit route. A bootstrapped product doesn't need that — and explicitly isn't going to do it.
  3. Slow growth is allowed. We don't want to grow faster than we can support. VC-backed apps can't make that choice.
  4. No acquisition risk. You're not building dependence on an app that Facebook buys next quarter and then rewrites the terms of use on.

That last point isn't hypothetical: many popular finance apps (Mint, Truebill, Personal Capital) have been acquired by larger financial institutions in the last ten years. Each time, the privacy regime changes and often the pricing model does too.

Why a sole proprietorship, not a B.V. (Dutch Ltd)

A reasonable question: why not incorporate as a B.V.? The answer is pragmatic. B.V. structures are useful when:

  • You're seeking investors (share structure)
  • You want to shield personal liability (large contracts, substantial staff)
  • You want to give a team equity

None of these situations apply to Okidoky now. A sole proprietorship is cheaper (no statutory annual audit, less administrative load), legally simpler, and for a small product with one maker just more fitting. If Okidoky grows into a team, the structure can change later.

What this means for you as a user: personal liability sits directly with the founder. For legal matters this means a more direct point of contact, not less protection — GDPR rights, consumer protection and all other regulations apply in full.

How big is "one person" really?

A reasonable concern: can one person actually manage all this? A finance app has code, infrastructure, security, support, legal compliance and product development all in one package.

The answer is: yes, up to a certain scale, and with the right tools. The stack is deliberately chosen to be manageable by one person without dropping quality:

  • Mollie for payments (PSD2-licensed, so no in-house fraud detection needed)
  • Hetzner for hosting (ISO 27001 certified, EU-based)
  • Plesk as management layer (proven server-management software)
  • Tesseract.js for OCR (open-source, local on the user's device — no cloud bill)
  • nodemailer SMTP for email (simple, controllable)
  • SQLite for the database (no DBA needed, simple to back up)

Every one of these choices has something in common: they are robust and stable, not attention-hungry. The app runs fine without someone tinkering with it daily.

What we will never do

Because there's no VC pressure, we can make a few promises that other apps can't back up:

  • No sale to a large bank or tech company. If we ever stop, we have an Open Source Pledge — the code goes public.
  • No data sale to third parties. There's no business model where that fits.
  • No dark-pattern features (fake scarcity, "only 3 Lifetime seats left", auto-renewal without notice).
  • No price hikes for existing Lifetime customers. A Lifetime of €25 stays €25. New pricing applies to new customers.

What this means in practice for you

If you're considering an app for your finances, "who's actually behind it" is a reasonable question — probably more important than feature lists. Three things to ask of any app:

  1. Where is the legal entity registered? (For us: KVK 98709364, Netherlands)
  2. How is revenue generated? (Subscriptions + limited ads — not data sales)
  3. What happens if the app shuts down? (Okidoky: 180 days advance notice + Open Source Pledge)

Three answers you can verify, not three marketing lines.

Okidoky is free to try, no credit card, no time pressure. And if you ever want to speak to the founder directly: info@okidoky.nl lands in the same inbox.