Our story
Some groups of friends talk about cars and holidays. Ours talked about databases — what broke, why it broke, and what the documentation quietly left out. Thirteen years later we're still having that conversation, just with more people in it.
That's where ORAcraft came from. Not from a business plan, but from a group of Oracle DBAs who found the work genuinely interesting, and who kept noticing the same thing on other people's estates: most of what goes wrong is avoidable. It goes wrong because somewhere along the way, someone decided “it'll hold” was good enough.
And yes, this site scrolls sideways on purpose. It's a database installer — next, next, next, finish. That's the joke, and we're aware it's a joke for us tech nerds, and maybe a couple of people will find it funny. These are the people we built it for. If you recognised it before reading this, you're in the right place.
Generic AI assistant
"Just increase UNDO_RETENTION and re-run the job — that should fix it."
Illustrative example — not a real customer conversation.
Our mission
One rule underneath everything: we show our work.
Prices are published on this site, not hidden behind a quote process. You have the live configurator to tailor the services exactly to your needs. A named senior DBA owning every engagement, so you know exactly who is doing the work. Everything is documented and handed over, so if you walk away you keep what we built.
None of that is clever. It's just uncommon — and it's the whole difference between a supplier you have to check and one you trust.
AI has made this sharper rather than softer. Answers are everywhere now, delivered with total confidence and no idea whether they're correct. On a production database, a confident wrong answer costs more than no answer at all. So nothing carries our name until it has been verified against a real system.
How we work
Some clients have one defined problem to solve. Some need senior capacity inside their own team. Some need an estate kept running, month after month. The commercial shape changes; the standard doesn't.
Senior only — no juniors learning on your production. Verified, not assumed. Documented, so there's no lock-in.
Which brings us to the part that actually matters: who does the work.
Thirteen years of delivering Oracle projects means working alongside a lot of people. Some excellent. Some less so. The ones we stayed in touch with are the ones who do things properly rather than getting away with them — who check before they commit, and who are bothered by details other people wave through.
Those are the people we've been gathering into ORAcraft, and we're still gathering them both locally and internationally.
Same principle as that first group of friends: you end up surrounded by people who care about the same things you do.
What they share isn't just competence. It's the belief that Oracle infrastructure work has a great deal of room for improvement — in the tooling, in the processes, in what gets accepted as normal. That's the thing ORAcraft is actually trying to do.
The service catalogue is where we start, not where we stop.
Step 01 — Understand
We start by truly listening. A focused 60-minute conversation. Just a senior expert asking questions about your workflows, bottlenecks, and goals.
Get started
Start with a free 60-minute scoping call with a senior DBA. No pitch deck — we look at what you actually have and tell you whether we're the right fit.
Sometimes the answer is that you don't need us. We'll say that too.