How we work
Different starting points. The same orbit.
Whether you bring code, an idea, or a legacy system, the work follows the same rhythm: a small first step, a fixed quote, weekly progress you can click, and a launch you can trust.
Three paths
Merge what exists. Build what doesn't. Modernize what's ageing.
The first two steps depend on where you start. From Launch onward, every path is the same: production in your accounts, then Orbit if you want us to keep it healthy.
Merge track · you have code
Nebula to orbit
Step 01
Scan
We audit your code, infrastructure, security, and running costs.
- You get
- Scored readiness report and fix roadmap
- Time
- 3–5 days
Step 02
Merge
We fix what's critical, refactor the hotspots, and add tests and CI.
- You get
- Reviewed pull requests in your repo
- Time
- 1–2 weeks
Step 03
Launch
Production hosting, domains, monitoring, backups, and a rollback plan.
- You get
- Live app and a runbook
- Time
- 1–3 days
Step 04
Orbit
Ongoing monitoring, patches, and small changes as you grow.
- You get
- Monthly health report
- Time
- Monthly
Build track · you have an idea
Spark to orbit
Step 01
Map
We scope the product, design the architecture, and fix the price.
- You get
- Spec, clickable prototype, and fixed quote
- Time
- ~1 week
Step 02
Build
Weekly sprints with a demo and a preview deploy every week.
- You get
- Working software, tested and reviewed
- Time
- 4–8 weeks
Step 03
Launch
Production hosting, domains, monitoring, backups, and a rollback plan.
- You get
- Live app and a runbook
- Time
- 1–3 days
Step 04
Orbit
Ongoing monitoring, patches, and new features as you grow.
- You get
- Monthly health report
- Time
- Monthly
Modernize track · legacy system
Old orbit to new
Step 01
Survey
We audit the system, data, and dependencies, and map the risks.
- You get
- Modernization plan and fixed quote
- Time
- 1–2 weeks
Step 02
Transfer
We migrate in stages, running old and new side by side. No big-bang cutover.
- You get
- Each slice live and verified
- Time
- Staged
Step 03
Launch
Final cutover with a tested rollback, then the old system is retired.
- You get
- Modern system live, legacy switched off
- Time
- Planned window
Step 04
Orbit
Monitoring, patches, and improvements on the new platform.
- You get
- Monthly health report
- Time
- Monthly
Principles
Six rules we don't bend.
They're why our projects stay cheap, quick, and safe, and why you can leave at any step without losing anything.
Fixed scope and quote
Agreed in writing before work starts. Changes are quoted before they're done.
Your repo from day one
All code lives in your repository and accounts. No lock-in, ever.
Weekly visibility
A short update and a preview link every week, so you always know where things stand.
Small, reviewed changes
Work lands as pull requests reviewed by a second engineer before it merges.
Security standard on everything
Every project passes the same ten checks before it goes live.
Documented handover
A runbook, architecture notes, and a call so you or your next hire can take over.
Every week
You'll never wonder what's happening.
About an hour of your time a week. The rest of it, you're talking to customers.
Mon
Plan
We confirm the week's goals with you.
Tue–Thu
Ship
Pull requests, reviews, and preview deploys.
Fri
Demo
A short demo or written update with a link you can click.
Handover
What you have when we're done.
Whether you stay in Orbit or take it from here, you leave with everything needed to run the product without us.
- Code in your repository, with a clean commit history
- CI pipeline running tests on every change
- Production deployed in your own accounts
- Monitoring and error alerts going to you
- Runbook: deploy, roll back, restore a backup
- Architecture notes and a recorded walkthrough
- Access removed and credentials rotated
FAQ
Working with us.
How much of my time does this need?
About an hour a week: a short kickoff, quick answers to questions, and the Friday demo.
Can I stop after one step?
Yes. Every step ends with something you keep: a report, a plan, merged code, or a live app.
What if I already have a developer?
Great. We can work alongside them, review their pull requests, or hand everything over to them at the end.
How do we communicate?
A shared Slack or email thread, whichever you prefer, plus the weekly update. No ticket portals.
Pick your starting point.
Tell us whether you have code or an idea. We'll suggest the smallest useful first step.