Accounts and access
Google Workspace or Microsoft 365, joiners and leavers, two-step sign-in for everyone, admin rights kept to the people who need them.
AI engineering department · IT, DevOps and software
Your engineering department, staffed and on call.
Olodu is an AI engineering department for companies with no CTO. It looks after the technology your company runs on: accounts and email, websites, servers, cloud, and the software your team depends on. One monthly price, response times in writing, and nothing on your systems changes without your OK.
The audit is read-only. No card, no contract, and you keep the report.
REQUEST 1042High
Website certificate expires in 6 days
- 09:14 Approved by Dana R., Operations director
- 09:15 Settings saved for rollback
- 09:16 Certificate renewed, job re-enabled
- 09:17 Independent re-check: valid for 89 days
For companies that have outgrown a freelancer and an IT shop, but do not have a CTO.
Nobody owns the technology
Logins, domains, the website, the cloud bill and the app all belong to "someone". When something breaks, everyone looks at each other.
Your IT provider stops at the laptop
Password resets and printers are covered. The deploy pipeline, the database and the integration that failed overnight are not.
The app needs a keeper
An agency or an app builder got you live. Now it needs updates, fixes and someone who answers at 2 a.m. when it goes down.
What we take off your plate
One team covers the whole stack, so a problem never falls between two providers.
Email and domains
DNS, email authentication (SPF, DKIM, DMARC), certificates and renewals, so mail lands in inboxes and nothing expires by surprise.
Websites and apps
Updates, bug fixes and small features for the software you already have, made in your repository and reviewed before they ship.
Servers and cloud
Patching, monitoring, backups with real restore tests, and a cloud bill that only pays for what you use.
Shipping changes
Deploy pipelines, staging environments and release checks, so a change goes out the same careful way every time.
When things break
Someone on call, a diagnosis with evidence, the fix, and a short written account of what happened and what changed.
How a request moves
The same four steps for a password policy or a production outage. You can see every one of them in your portal while it happens.
- 1
You tell us, or our checks do
Raise it in your portal in plain words. When a check we run for you goes red, we open the request ourselves.
- 2
We look first, read-only
An engineer gathers evidence and diagnoses the cause. A second reviewer, working separately, has to agree before a plan goes to you.
- 3
You approve the plan
What will change, the risk, how it will be undone if needed, and how we will prove it worked. Only the people you name can approve.
- 4
We do it and prove it
Settings are saved, the change is made, and an independent check runs. If that check fails, the change is rolled back automatically.
Trust is the whole job
Letting outsiders into your systems is a serious decision. These rules are built into how the work runs, not written in a policy nobody reads.
Read-only by default
We start with the least access that lets us look. Rights to change anything are a separate step that you approve, and you can withdraw them from your portal at any time.
Your approval before every change
Every change waits for a named approver at your company. Our own team cannot approve its own work, and a request cannot be closed by hand.
Saved state and automatic rollback
Before a change, the current settings are saved. After it, a check runs. Red means the saved state goes back and a person takes over.
A record you can export
Every look, decision, approval and result is written to a tamper-evident activity record. Download the whole thing whenever you like.
Compared with what you would do otherwise
| Olodu | IT provider | Freelancer | Hiring an engineer | |
|---|---|---|---|---|
| Covers IT, cloud and your code | Yes | IT only | Usually code | Depends on the hire |
| Someone on call at night | Growth and Department | Sometimes, extra | Rarely | One person |
| Fixed monthly price | Yes | Often | Hourly | Salary plus hiring cost |
| Knowledge stays when people leave | Written down per system | Partly | No | No |
| Every action recorded and exportable | Yes | Tickets only | No | No |
Three plans, priced by company size
Full plan details and response times →Start with a free 7-day audit
Read-only. We check your accounts, email security, backups, websites and cloud spend, then hand you a red/amber/green report with costs attached. If you want, we fix three things on it with your OK.
Guides for people who run the business, not the servers
All guides →
Systems auditWhat a free IT systems audit should check
Email securitySPF, DKIM and DMARC explained
Choosing supportAI engineering department vs managed IT
New to Olodu? Here is what we are and who is behind us.