we are oorik.
what we do
no surprises
in the small print.
- Sprint
- 14 days
- Demo
- Every Friday
- First reply
- 1 business day
- Code
- Your repo, commit one
- Exit
- Any sprint, 2 weeks' notice
- Pricing
- Quoted after the audit
how we work
- 01
Discovery & audit
1 week · audit
We map the problem with you and leave you a written brief you keep either way.
- 02
Scoping & architecture
1–2 weeks
A statement of work you approve before anyone writes code.
- 03repeats
Build
2-week sprints
Two-week sprints, a demo every Friday, commits landing in your repo.
- 04
QA & handoff
1–2 weeks
Real-device QA, automated checks, and docs your team will actually read.
- 05
Post-launch
Optional
Hand it off cleanly, or keep us on a retainer. No lock-in either way.
asked often.
Always. Your code lives in your repo from the first commit, under your branches and your reviews. There is no escrow, no staging in a private GitHub, and no IP held back at the end.
Every engagement starts with a one-week discovery and audit. We map the problem, audit what you already run, and come back with a written scope and a quote — with the risky parts named explicitly.
Pricing is decided after a meeting and an audit of your requirements — no figure survives contact with an unexamined system, so we do not publish one. You pay once for the build; an optional monthly retainer covers maintenance after handoff — and hosting too, if we run your servers.
You can stop at any sprint boundary with two weeks' notice, and you keep everything shipped, documented, and running. That clause is in every contract we sign, and it is why we would rather earn the next sprint than lock you into it.
Yes. We work in your stand-ups, your repo, and your roadmap when the project calls for it. We review your pull requests and you review ours; the aim is that your team can take the work over cleanly.
TypeScript, Python, Postgres, Kubernetes, and the LLM providers that earn their cost. We pick tools that have been in production for years rather than weeks, and we pick what your team can maintain after we leave.