No fixed address · Remote · Incident contact
Software. Security. Uptime.
The engineering partner for companies that cannot afford interesting weeks: we build the software, run the infrastructure, test the fences and answer the 3am call — No fixed address, Nigeria, working anywhere.
Direct
incident contact
Agreed
response commitments
7
engineering practices under one roof
2026
founded in Maiduguri
Terminal demo of the elbee CLI running an incident response: scan, contain, verify backups, deploy — with commentary.
What we do
Seven practices. One accountable team.
Every service is delivered by engineers who have been paged at 3am — so everything we build is built to be operated, not just demoed.
↳ open a deck — some of them do tricks
We build the software your business runs on: internal platforms, customer-facing products, APIs and the integrations that glue your stack together. Fixed scope where it can be fixed, weekly demos always, and code your own engineers will want to inherit — typed, tested, documented.
What you get
- Discovery workshop and architecture decision record
- Working software demoed weekly from week two
- CI/CD pipeline and automated test suite
- Handover documentation and team training session
- 90-day warranty on defects after launch
Companies whose off-the-shelf stack has hit its ceiling.
Pipelines, infrastructure as code and observability — deployments that stop being an event.
What you get
- Infrastructure and pipeline audit with risk register
- Terraform (or equivalent) coverage of your environment
- Deployment pipeline: build, test, scan, ship
- Monitoring, alerting and on-call runbooks
- Cost review — we usually find money here
Teams deploying by SSH and praying.
Web, mobile, network and social-engineering testing with a report your board will read.
report excerpt · client redacted
- CRITICAL ×1auth bypass — legacy API
- HIGH ×2over-privileged service tokens
- MEDIUM ×4stale dependencies · verbose errors
Retest included — we come back and try again after you fix it.
What you get
- Scoping call and rules of engagement (free)
- Manual exploitation, not just a scanner dump
- Report written as an attack narrative with CVSS-ranked findings
- Executive summary your board can act on
- Retest after remediation and attestation letter
Anyone signing enterprise deals, or answerable to a regulator.
Incident scoping, agreed containment support, a documented timeline and a practical recovery plan.
- 1 Contain
- 2 Preserve
- 3 Rebuild
- 4 Harden
What you get
- Direct incident contact with agreed availability
- Containment plan executed in hours, not days
- Forensic timeline and evidence preservation
- Root-cause analysis written for humans
- Hardening plan and 30-day follow-up check
Organisations that cannot afford a second breach.
Pipelines, dashboards and models — numbers your team argues with, not about.
What you get
- Data audit and metric definitions everyone signs
- Warehouse or lakehouse setup with tested pipelines
- Operational dashboards, refreshed automatically
- Forecasting or ML where the ROI is real
- Team enablement so you own it, not us
Companies drowning in spreadsheets and hunches.
Technical SEO, speed and structure — rankings built on engineering, not keyword stuffing.
What you get
- Technical SEO audit with prioritised fixes
- Core Web Vitals work (we are engineers, so it ships)
- Schema markup and crawl architecture
- Keyword-to-page map and content calendar
- Quarterly reporting tied to pipeline, not vanity metrics
Sites with traffic that should be converting.
Endpoints, identity, backup and a helpdesk — infrastructure nobody has to think about.
Illustrative service checklist
- endpointsoperational
- identity · sso · mfaoperational
- backupsrestore checks agreed in scope
- helpdesksupport targets agreed in scope
Monitoring and service targets are agreed for each engagement.
What you get
- Onboarding audit and written IT standard
- Endpoint management and patch policy
- Identity: SSO, MFA, least privilege
- Backup with quarterly tested restores
- Monthly report — the boring kind, on purpose
Teams with no IT department, or one that is drowning.
How we work
No mystery. No black boxes.
The same discipline whether we are writing your API or containing an incident: look first, decide in writing, show progress every week.
01
Listen
An hour on the phone beats a week of wrong assumptions. We start with what actually hurts, not what a brochure says you need.
02
Diagnose
We read the logs, the code and the invoices before we offer an opinion. Every engagement opens with findings in writing.
03
Execute
Weekly demos, always shippable. You watch the work land — and you can stop it any week it stops earning its keep.
04
Harden & hand over
Documentation, monitoring, runbooks and training. Success is you needing us less, not more.
Incident availability and response times are agreed for each engagement. +234 706 049 4655
Evidence and deliverables
Know what you will receive.
Example engagement plans. Scope, evidence and acceptance criteria are agreed before work starts.
Software and DevOps
Reliable delivery
- Architecture and dependency review
- Tested delivery pipeline and rollback exercise
- Monitoring, documentation and team handover
Penetration testing
A scoped security assessment
- Written scope and rules of engagement
- Evidence-backed findings and remediation priorities
- Retest results with an agreed report format
Response and managed IT
Incident readiness
- Incident contacts and escalation runbook
- Evidence-preservation and recovery procedures
- Backup restoration exercise and follow-up actions
Ask for supporting evidence
Request relevant reviewer credentials, a sample report and client references where sharing permission is available. Service commitments belong in the engagement agreement.
Discuss scope and evidenceLive systems
The engine room.
This panel shows the latest operations snapshot. It refreshes periodically and can connect to a configured external event stream. Demonstration incidents are simulated; missing or stale data is shown without presenting it as live production monitoring.
Platform status
awaiting first ingest…
- uptime · 30d
- —
- mean time to ack
- —
- mean time to resolve
- —
- stream rtt
- —
How it’s wired
external event source │ authenticated ingest ▼ /api/status → durable database │ ▼ latest snapshot + optional stream
The last successful snapshot remains visible when an external stream is unavailable. A stream requires a separately hosted event source; this site does not run a background simulation.
Website checks
Daily website and database probes. Availability reflects recorded samples over 30 days.
Loading recorded checks…
Who you're hiring
Engineers who have carried the pager.
elbulaturee was established in 2026 in Maiduguri, Borno State by engineers from fintech infrastructure and incident response — the people who built the systems and then carried the pager for them. We work remotely across Nigeria and with clients worldwide.
We kept meeting the same failure everywhere we looked: software built by people who never had to operate it, operated by people who never got to build it. Each side blamed the other while the customers paid the bill.
So we built the company we kept wishing existed — one team that writes the code, runs it, breaks into it on purpose and answers for it at 3am. Remote-first across GMT+1 (WAT), working with clients worldwide.
What a buyer will check
Founded: 2026, Maiduguri, Borno State — remote across Nigeria
Founder & Tech Lead: Sani Aminullah — saniaminullah7@gmail.com
Assessment evidence: Reviewer credentials and assessment scope agreed before engagement
References: References shared with client permission when available
Incident line: +234 706 049 4655
Response commitment: Incident availability and response times are agreed for each engagement.
Everything above is checkable. Ask us for the paperwork.
Direct
incident contact
Agreed
response commitments
7
engineering practices under one roof
2026
founded in Maiduguri
Straight answers
Questions we get before the first invoice.
Start here
Tell us what's on fire.
One form, five layers of spam defense on our side, a human on yours.
What happens next
Every submission is read by an engineer, not a sales bot. Replies within one working day.
- saniaminullah7@gmail.com
- +234 707 430 3610
- WhatsApp · +234 707 430 3610
Sani Aminullah — Founder & Tech Lead · saniaminullah7@gmail.com
- No fixed address, Nigeria
- Contact us to agree availability and response times
Active incident? Don't wait for email.
Contact us to discuss incident scope and availability.
Defense layers
- honeypothidden field only bots fill
- timingsub-second submits are bots
- validationschema enforced on both sides
- rate-limit5 submissions per 10 minutes
- deliverypersisted with audit trail