Ken 👨🏽‍💻

End-to-End Fullstack Engineer | System design specialist | I build scalable backend systems and craft pixel-perfect, high-performance user interfaces

[Ken 👨🏽‍💻 @ken_baz]

Hi, I'm Kenneth Bassey

I help businesses scale with robust fullstack solutions, from e-commerce platforms handling high traffic to logistics systems that streamline operations.

Stack: Python, TypeScript, Django, React/Next.js

Worked across E-commerce, Logistics, and EdTech. Currently exploring opportunities in Fintech.

DM for project inquiries.

[Big Smoke - @Skepta]

I am a British, Nigerian yes but I’ve always cared about Nigeria and anybody that has followed my career can vouch for that. I have houses in Nigeria, I want to take my kids home to a safe country just like we travel the rest of the world. Why should I not speak up about what is happening in my homeland?

[Glenn Hoddle @GlennHoddle]

This was such fun doing !!😂. Teddy on the bike at the end kills me !!!!😂😂😂.

[Faceless Dev 🎭 @_fusionTech]

I remember when I started building StackShift and was using SES for emails.

When I got closer to launch, I applied for SES production access so StackShift could send real emails to users, not just the one verified email I was using in sandbox.

AWS kept rejecting it.

They were asking for so many things I didn’t have yet: clearer use case, sending patterns, bounce handling, complaint handling, suppression strategy, opt-in details, domain setup, abuse prevention, and all the things you’re expected to already understand before you can even send email properly.

At that point, I moved to Resend so I could keep shipping.

But the thought stayed in my head:

Why is this not a StackShift feature?

If StackShift is supposed to help developers deploy and run real applications, then transactional email is part of that story.

Apps need to send emails for several things.

So instead of depending on yet another external service, I decided to build StackShift Mail.

Not as a wrapper around SES.
Not as a wrapper around Resend.
Not as a wrapper around Mailgun.
Actual StackShift-owned mail infrastructure.
The flow now is:

App calls StackShift Mail
→ message is stored
→ send job is queued
→ worker composes the email
→ DKIM/signing path is handled
→ Postfix hands it off
→ attempts/logs/status are tracked
→ failures can be retried
→ bounces can be processed
→ bad recipients can be suppressed

And the most interesting part is that StackShift Mail is powered by another StackShift primitive I already built: StackShift Jobs.

StackShift Jobs is the durable background execution system I built for work that should not die when the request ends.
Instead of doing everything inside an HTTP request, you can offload work to StackShift Jobs and let it handle retries, attempts, logs, delayed execution, failures, and recovery.
That means Mail does not have to block the user’s request.
When you call mail.send, StackShift can accept the message, queue the work, process it safely, retry temporary failures, and keep a full trail of what happened.
That same Jobs system also powers things like OTP expiry, webhook delivery retries, bounce processing, scheduled sends, batch sending, and reputation evaluation.
This is why building platform primitives matters.
One primitive unlocks another.
So far, StackShift Mail now has:
transactional email sending
API-key scoped usage
message persistence
send attempts
logs
Postfix handoff
DKIM/signing integration path
customer domain verification
SPF/DKIM/DMARC/return-path checks
sender domain enforcement
bounce handling
hard/soft bounce classification
suppression lists
automatic blocking of bad recipients
OTP send and verify
OTP expiry
max attempts
resend cooldowns
hashed OTP storage
templates
template versions
backend template rendering
template preview
test sends
sendTemplate API
mail lifecycle events
webhooks
webhook signing
webhook retries
message timeline
reputation checks
sending limits
warmup stages
domain reputation
scheduled emails
transactional batches
attachments
inbound mail foundation
analytics, etc.

This started because I got blocked trying to send emails for StackShift.
Now it’s becoming a full StackShift product.
Deploy the app.
Run the jobs.
Send the emails.
Track what happened.

[Ken 👨🏽‍💻 @ken_baz]

Again, why haven’t you tried StackShift yet, why I ask.

[Faceless Dev 🎭 @_fusionTech]

I remember when I started building StackShift and was using SES for emails.

When I got closer to launch, I applied for SES production access so StackShift could send real emails to users, not just the one verified email I was using in sandbox.

AWS kept rejecting it.

They were asking for so many things I didn’t have yet: clearer use case, sending patterns, bounce handling, complaint handling, suppression strategy, opt-in details, domain setup, abuse prevention, and all the things you’re expected to already understand before you can even send email properly.

At that point, I moved to Resend so I could keep shipping.

But the thought stayed in my head:

Why is this not a StackShift feature?

If StackShift is supposed to help developers deploy and run real applications, then transactional email is part of that story.

Apps need to send emails for several things.

So instead of depending on yet another external service, I decided to build StackShift Mail.

Not as a wrapper around SES.
Not as a wrapper around Resend.
Not as a wrapper around Mailgun.
Actual StackShift-owned mail infrastructure.
The flow now is:

App calls StackShift Mail
→ message is stored
→ send job is queued
→ worker composes the email
→ DKIM/signing path is handled
→ Postfix hands it off
→ attempts/logs/status are tracked
→ failures can be retried
→ bounces can be processed
→ bad recipients can be suppressed

And the most interesting part is that StackShift Mail is powered by another StackShift primitive I already built: StackShift Jobs.

StackShift Jobs is the durable background execution system I built for work that should not die when the request ends.
Instead of doing everything inside an HTTP request, you can offload work to StackShift Jobs and let it handle retries, attempts, logs, delayed execution, failures, and recovery.
That means Mail does not have to block the user’s request.
When you call mail.send, StackShift can accept the message, queue the work, process it safely, retry temporary failures, and keep a full trail of what happened.
That same Jobs system also powers things like OTP expiry, webhook delivery retries, bounce processing, scheduled sends, batch sending, and reputation evaluation.
This is why building platform primitives matters.
One primitive unlocks another.
So far, StackShift Mail now has:
transactional email sending
API-key scoped usage
message persistence
send attempts
logs
Postfix handoff
DKIM/signing integration path
customer domain verification
SPF/DKIM/DMARC/return-path checks
sender domain enforcement
bounce handling
hard/soft bounce classification
suppression lists
automatic blocking of bad recipients
OTP send and verify
OTP expiry
max attempts
resend cooldowns
hashed OTP storage
templates
template versions
backend template rendering
template preview
test sends
sendTemplate API
mail lifecycle events
webhooks
webhook signing
webhook retries
message timeline
reputation checks
sending limits
warmup stages
domain reputation
scheduled emails
transactional batches
attachments
inbound mail foundation
analytics, etc.

This started because I got blocked trying to send emails for StackShift.
Now it’s becoming a full StackShift product.
Deploy the app.
Run the jobs.
Send the emails.
Track what happened.

[Faceless Dev 🎭 @_fusionTech]

First paid user on Stackshift. 🚀🎉🥳

[Faceless Dev 🎭 @_fusionTech]

@hiayoola @getkirki You can ship any Wordpress project right from my platform in just a few clicks.

[Faceless Dev 🎭 @_fusionTech]

Pushed WordPress much further on StackShift.

It's not just a template. (Legacy)

Now you can:

- Create WordPress directly
- Launch multisite networks
- Import existing installs
- See WordPress/PHP/runtime/storage/DB health at a glance
- Install themes
- Run safe actions like core updates, maintenance mode, permalinks flush, and admin reset
- Deploy on StackShift managed server, your VPS, or Cloud account, etc.

If you’re a WordPress designer, builder, or agency, I’d love to show you what we’re building.

[Faceless Dev 🎭 @_fusionTech]

Deployment on Stackshift

[Ken 👨🏽‍💻 @ken_baz]

This is just amazing 🔥 🔥

[Faceless Dev 🎭 @_fusionTech]

Deployment on Stackshift

[Faceless Dev 🎭 @_fusionTech]

I deployed my portfolio on @StackshiftCloud, build time was 00.23s and I deployed the same project on another platform, build time was 00.54 seconds. I tried with 3 different projects and Stackshift still built and deployed faster.

Deploy on Stackshift today, you can even bring your cloud account (Hertzner, AWS, Azure, Digital Ocean) or VPS, plug it on Stackshift and deploy from your GitHub straight to your own server if you don’t want to deploy to Stackshift servers.

[Ken 👨🏽‍💻 @ken_baz]

If you are not using StackShift for your deployments, you’re wrong! This is amazing 🔥

[Faceless Dev 🎭 @_fusionTech]

Today I'm launching StackShift.

StackShift is an infrastructure ownership platform for deploying, operating, and managing modern software from one control plane.

It supports Node.js, Python, Go, Rust, PHP, Laravel, Ruby, static sites, Docker-based apps, Svelte/SvelteKit, worker services, multi-container stacks, and web3-style build workflows like Hardhat, Truffle, Foundry, and Anchor.

But StackShift is not just about deployment.

It brings together hosted infrastructure, bring-your-own server, bring-your-own cloud, bring-your-own SMTP or outbound email provider, database provisioning, domain purchases, DNS management, email hosting, WordPress and other deployable templates, logs, metrics, backups, billing, teams, and AI-assisted failure diagnosis.

The thesis is simple:

Modern teams should not have to choose between convenience and ownership.

StackShift gives teams one place to run their software infrastructure, whether it lives on StackShift, their own server, their own cloud account, or their own providers.

I wrote more about the product direction, the ownership model, and what I’m building here:
https://t.co/AWoboSSFrk
You can also checkout StackShift here:
https://t.co/zLrztszIDt

[Faceless Dev 🎭 @_fusionTech]

Today I'm launching StackShift.

StackShift is an infrastructure ownership platform for deploying, operating, and managing modern software from one control plane.

It supports Node.js, Python, Go, Rust, PHP, Laravel, Ruby, static sites, Docker-based apps, Svelte/SvelteKit, worker services, multi-container stacks, and web3-style build workflows like Hardhat, Truffle, Foundry, and Anchor.

But StackShift is not just about deployment.

It brings together hosted infrastructure, bring-your-own server, bring-your-own cloud, bring-your-own SMTP or outbound email provider, database provisioning, domain purchases, DNS management, email hosting, WordPress and other deployable templates, logs, metrics, backups, billing, teams, and AI-assisted failure diagnosis.

The thesis is simple:

Modern teams should not have to choose between convenience and ownership.

StackShift gives teams one place to run their software infrastructure, whether it lives on StackShift, their own server, their own cloud account, or their own providers.

I wrote more about the product direction, the ownership model, and what I’m building here:
https://t.co/AWoboSSFrk
You can also checkout StackShift here:
https://t.co/zLrztszIDt

[Akwaman @akwa_man]

Please Sir @DONJAZZY give me my 50% let me go 😂😂😂😂😂

[Ken 👨🏽‍💻 @ken_baz]

Hi, I'm Kenneth Bassey

I help businesses scale with robust fullstack solutions, from e-commerce platforms handling high traffic to logistics systems that streamline operations.

Stack: Python, TypeScript, Django, React/Next.js

Worked across E-commerce, Logistics, and EdTech. Currently exploring opportunities in Fintech.

DM for project inquiries.

[Ken 👨🏽‍💻 @ken_baz]

Recently I have noticed that you don’t see errors about network connectivity on your feeds anymore instead you get your last cached results when there’s connectivity issues
This is the beauty of modern design resilience pattern where your system degrades instead of a complete cascade breakdown

[Mari @Tech_girlll]

Day 16 of learning system design

I learnt about Sharding and how it connects to Database Replication.

Sharding basically means splitting a large database into smaller, more manageable pieces called shards. Each shard holds a portion of the data, which helps distribute the load and improve performance, especially when your app scales.

Replication, on the other hand, means making copies of your database across multiple servers. It ensures data availability, fault tolerance, and quick recovery if one server goes down.

Here’s how they connect:
Replication keeps copies of each shard across multiple servers, so even if one shard fails, the system still runs smoothly using the replicated copy.

Sharding handles scale, replication handles reliability, together, they keep large systems fast and resilient.

Still using the System Design Primer on GitHub for this journey, and it’s been eye-opening
Hold me accountable❤️

[Ken 👨🏽‍💻 @ken_baz]

@aidenybai - IDE: Vs code
- code agent: Claude pro
- bundler: vite
- styling: Tailwindcss
- animation: Framer motion

[Ken 👨🏽‍💻 @ken_baz]

@rqobela Python 🤝🏽

[Ken 👨🏽‍💻 @ken_baz]

𝗔 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝗳𝗼𝗿 𝗖𝗵𝗼𝗼𝘀𝗶𝗻𝗴 𝗬𝗼𝘂𝗿 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲

We have monoliths, microservices, event-driven, and serverless. The architectural options are endless. The real skill isn't defining them, it's knowing when and why to choose one over another.

Here are the 5 critical constraints I use to evaluate any architectural decision:
- 𝗦𝘆𝘀𝘁𝗲𝗺 𝗖𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆: Simple CRUD vs. multiple business domains? (Complexity often dictates distribution).
- 𝗘𝘅𝗽𝗲𝗰𝘁𝗲𝗱 𝗦𝗰𝗮𝗹𝗲: Hundreds of users? Stick to simplicity. Thousands? Scalability is your 1 constraint.
- 𝗧𝗲𝗮𝗺 𝗦𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲: A small team will be crushed by microservices overhead. Large teams are perfectly structured for distributed systems.
- 𝗧𝗶𝗺𝗲 𝘁𝗼 𝗠𝗮𝗿𝗸𝗲𝘁 (𝗧𝗧𝗠): Need to ship fast? Simplicity wins. (Think monoliths or serverless early on).
- 𝗥𝗲𝗴𝘂𝗹𝗮𝘁𝗼𝗿𝘆/𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆: Domains like FinTech or Healthcare demand strict data separation, which can force your architectural hand.

𝗧𝗵𝗲 𝟰-𝗦𝘁𝗲𝗽 𝗦𝗲𝗹𝗲𝗰𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝗰𝗲𝘀𝘀:
- 𝗗𝗲𝗳𝗶𝗻𝗲 𝘁𝗵𝗲 𝗡𝗼𝗿𝘁𝗵 𝗦𝘁𝗮𝗿: What are your business/technical Goals? (Cost, speed, fault tolerance).
- 𝗟𝗶𝘀𝘁 𝗖𝗼𝗻𝘀𝘁𝗿𝗮𝗶𝗻𝘁𝘀: Document all limitations (Latency, team size, compliance).
- 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝘆 𝗖𝗮𝗻𝗱𝗶𝗱𝗮𝘁𝗲𝘀: Brainstorm 2-3 patterns that fit the goals.
- 𝗘𝘃𝗮𝗹𝘂𝗮𝘁𝗲 𝗧𝗿𝗮𝗱𝗲-𝗼𝗳𝗳𝘀: Check the pros/cons. Which option mitigates the greatest long-term risk?

Architecture is a deliberate decision, not a default.