Oxura, international
Direct communication and full ownership — not a black box, and not a layer of account managers between you and the people building your product.
The delivery model
- Who you talk to: the people building your product, not a separate account manager layer.
- Where engineering happens: primarily Kathmandu, Nepal — with local offices in Houston, Texas and Birmingham, UK.
- Communication cadence: regular demos and async written updates between calls.
- Tools: whatever your team already uses for messaging, issue tracking, and version control — we adapt to your stack, not the other way around.
Working hours
Birmingham (our UK office)
UTC+0 / +1
Nepal afternoon overlaps Birmingham's morning and midday
Houston (our US office)
UTC-6 / -5
Nepal evening overlaps Houston's early morning
Sydney
UTC+10 / +11
Nepal morning overlaps Sydney's afternoon
Typical overlap — shifts by roughly an hour depending on daylight saving.
What to expect
Documentation
Decisions and architecture written down, not just discussed on a call.
Code review & CI/CD
Nothing reaches production without review and automated checks.
Regular demos
Working software shown on a cadence, not a surprise at the end.
Async-first updates
Progress doesn't wait for a synchronous meeting to be visible.
Full IP and code ownership, and an NDA on request before any discovery work begins. See security & ownership for the details.
Begin
Tell us about your product and team — we'll figure out the right engagement model together.