Vorluno // software studio
Software, built with intent.
// the studio that builds niiko — and takes on a handful of client builds with the same crew.
| approach | full-stack, one team, no handoffs |
| stack | TypeScript · Python · shipped, not staged |
| status | niiko live today — building the next module in public |
the studio
A software studio that ships its own product first — then builds yours with the same standard, not a special version of it.
// Vorluno runs on one rule: everything we ship has to survive production. We prove it daily on niiko, our own platform — and we bring the same team, stack and standard to a small number of client builds.
what we build
Six things we do extremely well.
// Full builds or focused engagements — always the same team end-to-end, in English, from Panamá (UTC-5) for clients worldwide.
- 01
Product engineering
From first scope to production: web apps and SaaS built end-to-end by the same people who designed them. No handoffs, no telephone game.
- 02
AI-native features
Assistants, retrieval and automation wired into the product — not bolted on. The same intelligence layer we build for niiko, applied to your domain.
- 03
Integrations & automation
Your tools, finally talking: WhatsApp and Meta APIs, payments, ERPs — data that moves without a human re-typing it.
- 04
Design engineering
Interfaces with actual craft — typography, motion and detail at award level, engineered for performance, not decorated after the fact.
- 05
Data & financial backends
Numbers you can trust: reconciled, auditable, multi-currency. Backends where correctness is the feature.
- 06
Run & iterate
We stay after launch — monitoring, support and a roadmap that keeps shipping. Software is a relationship, not a delivery.
the product
niiko — one platform,
every part of your business.
// One workspace where every module shares one client record — from the first WhatsApp to the last invoice. Pick a module.
Miira
An AI agent that answers and qualifies every lead over WhatsApp — in real time, day or night.
- Every inbound lead answered in seconds — WhatsApp or email
- Scored and routed while you sleep
- Consent-first: never a cold WhatsApp
CRM
Every client, deal and conversation on one timeline that reflects reality — not one you have to feed.
- A pipeline you can actually read
- Full history on every contact — filled in from the work, not by hand
- Saved views instead of static segments
Ciita
Scheduling on your real availability: a booking page anyone opens without an account, and appointments the agent proposes from that same calendar.
- A booking page anyone opens — no account required
- The agent proposes times from your real calendar
- One availability, not one per tool
Kiipu
Collections that don't chase people — payment links, reminders that go out on their own, receipt photos read by AI, and a ledger that always balances.
- Payment links and plans, with reminders that go out on their own
- Upload a receipt — AI reads it, a human confirms
- A collections agent that never negotiates a discount
Fiilz
The work you deliver, project by project: pieces with their versions, an assigned approver, and the client approving or asking for changes on a screen of their own.
- Versions per piece — no «final_v3_REAL»
- One named approver, not a group chat
- The client approves or asks for changes on their own screen
Riinda
Your team, looking inward: what needs attention, who is carrying what, and who can take the next thing without being buried.
- Who is carrying what, without a status meeting
- What is waiting on a person, not on a stage
- Reads the work already in niiko — no second board
Niima
From the yes to the signature: proposals built from your own catalogue, accepted from the client's phone, and the contract signed right there.
- Proposals from your own catalogue, in minutes
- Accepted from the client's phone
- The contract signed in the same path — one flow, not two tools
Inbox
WhatsApp and email in one thread — so nothing falls through the cracks between apps.
- WhatsApp + email, one thread
- Knows the 24-hour window so messages don't bounce
- Autopilot until a human takes over — then it steps back
Notes
Knowledge tied to the work — not another folder graveyard nobody opens.
- Linked to clients and deals, not lost in folders
- One page of truth per relationship
- Search that actually finds things
01 / 06
Explore every module in depth →the proof
Vorluno doesn't show you case studies.
We show you what we bet the company on.
// niiko is the platform Vorluno runs on — the same CRM, the same inbox, the same AI agent qualifying our own leads. It ships in public, every week. If it breaks, we feel it first. That's the proof: not a slide deck, a product we can't afford to get wrong.
how we ship
Weeks, not quarters.
// The same loop for client work and for niiko. You see progress every week — clickable, in staging, never a slide.
Scope
One week. We map the problem, cut it to what actually matters, and fix the first milestone.
you get · a plan with a priceBuild
Weekly drops you can click. TypeScript & Python, tested, in staging from week one.
you get · a working app, weeklyShip
Production with observability, docs and a runbook — not a handover PDF.
you get · a launch, documentedRun
We stay on: support, iteration and the next milestone on a public roadmap.
you get · a team that stayswho you work with
At Vorluno, the person who scopes it is the person who ships it.
// Vorluno is a founder-led studio — José González is the same hands on the architecture, the code, and the call with you. No account managers, no relay, no telephone game. We take a small number of builds at a time on purpose, so the person who plans your software is the one who writes it.
// on LinkedIn →shipping in public
Changelog
for developers
Built to build on.
// The door to the platform's documentation, opening as we do. Nothing here is live yet — when it is, it'll be real, not a placeholder.
How niiko works, module by module.
soonBuild on top of your own workspace.
soonPatterns and playbooks from shipping in public.
soonplain answers
Things people actually ask.
Do you take client work while building niiko?+
Yes — Vorluno takes a small number of client builds at a time while building niiko. The studio funds the product, and the product keeps Vorluno honest: everything we recommend to you, we run ourselves.
What stack do you work in?+
Vorluno works in TypeScript (Next.js, NestJS) and Python (FastAPI) on PostgreSQL. If your problem needs something else, we'll say so instead of forcing it.
Where are you based, and in what timezone?+
Vorluno is based in Panamá (UTC-5), working in English with clients worldwide. Overlap with US timezones is full; with Europe, mornings.
How do we start?+
One call, then a one-week scope. You leave with a plan and a price — whether you build with us or not.
How much does a build cost?+
Every build is scoped before it's priced, so the number fits the work — not a package you're squeezed into. You get a fixed price for the first milestone before we start, and no hourly surprises after. The one-week scope is where that price comes from.
Who owns the code and the IP?+
You do. Everything Vorluno builds for you is yours — code, data and accounts. We hand over everything at the end, and we never hold your product hostage.
What if it doesn't work out?+
The one-week scope is deliberately low-commitment: you leave with a plan and a price whether you build with us or not. If we're not the right fit, we'll say so — and the scope is yours to keep.
Will you sign an NDA?+
Gladly. Send yours or use ours — either way, before you share anything sensitive.
Can we use niiko too?+
niiko is Vorluno's own platform, opening to a small number of teams. If your operation is agency-shaped — leads, clients, conversations, collections — tell us and we'll say honestly whether it fits you yet.
// get started
Let's build something
that has to work.
One call. A one-week scope. A plan with a price.
Talk to us →