
Backend-heavy Full-Stack Engineer | Scalable APIs, auth & backend systems for startups and companies. | Creator of @_reqit
i can cook
Joined August 2025
- Tweets7.2K
- Following921
- Followers845
- Likes6K
Hey, I'm HalxDocs.
I'm a backend-focused engineer who loves building software, open-source tools, and developer tools.
I mostly work with Go and TypeScript, building production-ready APIs, backend infrastructure, and distributed systems. I'm also diving deeper into infrastructure engineering and distributed systems.
I've built and shipped projects like Reqit, an open-source, local-first API client, alongside other tools and experiments.
I enjoy solving problems, learning new things, and turning ideas into working software.
I'm currently open to full-time opportunities, internships, and remote backend development roles.
I'd love to connect with founders, engineers, and teams working on interesting products.
Check out my portfolio to learn more about what I do and what I've built:
🌐 halxdocs.com
If you have an opportunity or know a team looking for a backend developer, my DMs are open.
HalxDocs retweeted
Got our first support on @afro_launch with the help of @myhappr 🥳
You like my work?
Support me here
myhappr.com/halxdocs
HalxDocs retweeted
Hi, I’m Tumi and these are my favourite designs. #GraphicDesigner
HalxDocs retweeted
Buymeacoffee but for Africans. myhappr.com
HalxDocs retweeted
Replying to @senviok
@senviok just shipped Senviok Mailbox.
Beyond transactional and marketing emails, you can now view, respond to, and manage every email sent to and from your domain, right from your Senviok dashboard.
...Emails for your app and your operations.
Your mailbox just got a new home !
Introducing @senviok Mailbox , a new way to receive, manage, and stay on top of your mail. Receive emails in your inbox and more.
It's live. It's here. And it's time you checked it out. 👀
Watch the launch. Experience the difference.
HalxDocs retweeted
Haildesk now has Identity Verification! 🚀
Businesses can now securely verify their logged-in customers, preventing people from impersonating other customers through the chat widget.
Support agents can also see whether a customer is verified before sharing sensitive account information.
And if a customer is already logged in, they no longer have to enter their email again to start a conversation.
Live now on Haildesk! 🔐
haildesk.com/docs#identifyin…
Whop now has a team on the ground in Lagos, Nigeria.
Here's why:
15,000+ businesses sign up on Whop every day. We sort every one into 70,000+ categories, from roofing to makeup consulting, so we can see what's working & where demand is.
We're building everything you need to go from $0 to $10M (websites, ads, investing, payments, etc) but the missing piece is more hungry entrepreneurs.
Nigeria has 230M+ people, a median age of 18, and some of the hungriest founders I've ever met.
That's why we're taking the bet that the next wave of big businesses won't only come from the West, but also places like Nigeria, Chad, Pakistan, Uganda, etc, where young & hungry dreamers are abundant.
Here is a blog on it
Enjoy.
halxdocs.com/blog/signed-run…
reqit 2.6.0: every request leaves a signed receipt
Ever tried to answer “what exactly did we send?” a day after an incident? Usually it is memory, a screenshot, and a token that has since rotated.
reqit 2.6.0 changes that. Every execution now writes a run receipt to .reqit/runs/.
A receipt records:
the request as written, with {{variables}} intact
where each variable came from — never its value
response status, safe headers, timing, and a SHA-256 of the body
a hash link to the previous receipt
an HMAC-SHA256 signature keyed from your OS keychain
Redaction happens before anything reaches disk: query values outside a safe allowlist, credential-shaped path segments and unknown header values are masked. Bodies are stored as hashes, not content. You can attach a receipt to a ticket or commit it without a secret sweep.
Verify anytime:
reqit runs verify
✓ 128 receipts verified — hashes and chain intact
Or open Trust → Run receipts in the desktop app for the same history in a UI.
What it is not: tamper-proof. It is tamper-evident — editing a receipt breaks the chain, and recomputing the chain still fails the signature without your key. Redaction is defense in depth, and recording stays best-effort so it can never fail a request. Those limits are documented.
Changelog: github.com/HalxDocs/reqit/bl…
Release: github.com/HalxDocs/reqit/re…
Shipped in 59 commits, with signed receipts across the app, CLI, runner, scheduler, MCP server and event replay.
HalxDocs retweeted
Want to create desktop apps that pop? 💥 You can use Flutter’s experimental windowing APIs to take your desktop app to the next level!
@Canonical and Google have partnered to build native, cross-platform multi-window support for Flutter on desktop (macOS, Windows, Linux).
#FlutterCreate
Here is a blog on it
Enjoy.
halxdocs.com/blog/signed-run…
reqit 2.6.0: every request leaves a signed receipt
Ever tried to answer “what exactly did we send?” a day after an incident? Usually it is memory, a screenshot, and a token that has since rotated.
reqit 2.6.0 changes that. Every execution now writes a run receipt to .reqit/runs/.
A receipt records:
the request as written, with {{variables}} intact
where each variable came from — never its value
response status, safe headers, timing, and a SHA-256 of the body
a hash link to the previous receipt
an HMAC-SHA256 signature keyed from your OS keychain
Redaction happens before anything reaches disk: query values outside a safe allowlist, credential-shaped path segments and unknown header values are masked. Bodies are stored as hashes, not content. You can attach a receipt to a ticket or commit it without a secret sweep.
Verify anytime:
reqit runs verify
✓ 128 receipts verified — hashes and chain intact
Or open Trust → Run receipts in the desktop app for the same history in a UI.
What it is not: tamper-proof. It is tamper-evident — editing a receipt breaks the chain, and recomputing the chain still fails the signature without your key. Redaction is defense in depth, and recording stays best-effort so it can never fail a request. Those limits are documented.
Changelog: github.com/HalxDocs/reqit/bl…
Release: github.com/HalxDocs/reqit/re…
Shipped in 59 commits, with signed receipts across the app, CLI, runner, scheduler, MCP server and event replay.
reqit 2.6.0: every request leaves a signed receipt
Ever tried to answer “what exactly did we send?” a day after an incident? Usually it is memory, a screenshot, and a token that has since rotated.
reqit 2.6.0 changes that. Every execution now writes a run receipt to .reqit/runs/.
A receipt records:
the request as written, with {{variables}} intact
where each variable came from — never its value
response status, safe headers, timing, and a SHA-256 of the body
a hash link to the previous receipt
an HMAC-SHA256 signature keyed from your OS keychain
Redaction happens before anything reaches disk: query values outside a safe allowlist, credential-shaped path segments and unknown header values are masked. Bodies are stored as hashes, not content. You can attach a receipt to a ticket or commit it without a secret sweep.
Verify anytime:
reqit runs verify
✓ 128 receipts verified — hashes and chain intact
Or open Trust → Run receipts in the desktop app for the same history in a UI.
What it is not: tamper-proof. It is tamper-evident — editing a receipt breaks the chain, and recomputing the chain still fails the signature without your key. Redaction is defense in depth, and recording stays best-effort so it can never fail a request. Those limits are documented.
Changelog: github.com/HalxDocs/reqit/bl…
Release: github.com/HalxDocs/reqit/re…
Shipped in 59 commits, with signed receipts across the app, CLI, runner, scheduler, MCP server and event replay.
HalxDocs retweeted
WE ARE LIVE! 🚀🎉
After months of building, @olenar_edu has officially launched!
Courses, mentorship, and community, all in one platform.
Whether you're here to learn or teach, there's a place for you.
Explore Olenar today: olenar.org
🤖 Made with AI
reqit 2.6.0: every request leaves a signed receipt
Ever tried to answer “what exactly did we send?” a day after an incident? Usually it is memory, a screenshot, and a token that has since rotated.
reqit 2.6.0 changes that. Every execution now writes a run receipt to .reqit/runs/.
A receipt records:
the request as written, with {{variables}} intact
where each variable came from — never its value
response status, safe headers, timing, and a SHA-256 of the body
a hash link to the previous receipt
an HMAC-SHA256 signature keyed from your OS keychain
Redaction happens before anything reaches disk: query values outside a safe allowlist, credential-shaped path segments and unknown header values are masked. Bodies are stored as hashes, not content. You can attach a receipt to a ticket or commit it without a secret sweep.
Verify anytime:
reqit runs verify
✓ 128 receipts verified — hashes and chain intact
Or open Trust → Run receipts in the desktop app for the same history in a UI.
What it is not: tamper-proof. It is tamper-evident — editing a receipt breaks the chain, and recomputing the chain still fails the signature without your key. Redaction is defense in depth, and recording stays best-effort so it can never fail a request. Those limits are documented.
Changelog: github.com/HalxDocs/reqit/bl…
Release: github.com/HalxDocs/reqit/re…
Shipped in 59 commits, with signed receipts across the app, CLI, runner, scheduler, MCP server and event replay.
wrote a little note about how i implemented reqit's HTTP request execution engine in Go.
halxdocs.com/blog/http-reque…
HalxDocs retweeted
Hey guys! I'm looking for a remote, full-time Software Engineer role in backend, frontend, or AI.
I've built real-world products processing millions of naira and serving hundreds of users.
Portfolio: samueltuoyo.com
Retweets appreciated. 🙏























