Stackshift

Introducing Stackshift We're building the hosting platform developers deserve. Here's why ↓

@abolorreeeee @mikailhamzat Checkout stackshift.cloud and get affordable VPS, you can also manage it right on StackShift and deploy your projects straight from GitHub.

@mikailhamzat @StackshiftCloud I’ve been sleeping on VPs since o

Best decision I made earlier last year. Reduced my production cost to the bare minimum. Meanwhile, to manage your VPS, Check out @StackshiftCloud on Afrolaunch 🌍 afrolaunch.com/startups/stack…

@mikailhamzat You know ball, bro. Thank you.🙏

Man! I’m really cooking something on @StackshiftCloud for Mobile Devs, we aren’t going to just focus on web.

I forgot that I shipped these two features last week on @StackshiftCloud. S3-compatible object storage & Terraform Support. You can now create buckets on StackShift from the dashboard, the API, or Terraform. Creation returns an access key and secret once. From there, anything that speaks S3 works: the AWS CLI, boto3, any S3 SDK. The data plane authenticates with SigV4, the same scheme AWS uses. No custom client. No migration wrapper. You change the endpoint, everything else stays the same. Buckets are private by default. Mark one public and objects are anonymously GET-able... Useful for assets, build artifacts, public files. Multipart uploads and Range GETs are supported. No egress fees. If you attach a bucket to a project at creation time, the credentials and endpoint get injected into that project's environment automatically. Terraform/OpenTofu provider The stackshift provider covers the full lifecycle and not just infrastructure state, but operations too. Declarative resources: - stackshift_project: Project with GitHub repo, runtime, region, build/start commands - stackshift_project_env: Environment variable sets per environment - stackshift_database: Managed Postgres, MySQL, or Redis - stackshift_domain: Custom domain mapping - stackshift_dns_record: DNS records on StackShift-registered domains - stackshift_bucket: S3 bucket with credentials (coming) - stackshift_compute_instance: Provision a compute node, with optional StackShift agent installation Operational resources (imperative actions modeled as Terraform resources with a nonce for re-triggering): - stackshift_build_action: Trigger a build for a project - stackshift_deployment_action: Deploy, rollback, or other deployment operations against a project - stackshift_runbook: Define a runbook as code (command, parameters, approval gates, environments) - stackshift_runbook_execution: Execute a runbook version, with parameters and optional approval For agencies: - stackshift_agency_client: Manage a client record - stackshift_agency_resource_assignment: Assign resources (projects, databases, etc.) to clients Data sources for stackshift_project, stackshift_database, and stackshift_database_credentials are included for referencing existing resources. Auth is an API token "STACKSHIFT_API_TOKEN" or declared in the provider block. plan, apply, destroy, and import all work. What this looks like end-to-end One .tf file can declare a project, its managed database, its storage bucket with credentials auto-injected into the project environment, its domain, DNS records, a runbook for migrations, and trigger the first build and deployment all in a single terraform apply. For agencies managing multiple clients on StackShift, this means the entire client onboarding, infra, access keys, resource assignments can be templated and applied in one shot.

Sharing a mobile build with your team before it hits the Play Store or App Store is still surprisingly painful. You're emailing APKs, pinging people on WhatsApp, or cobbling together Firebase App Distribution with yet another tool you have to manage. We just shipped mobile distribution on StackShift, built for exactly that gap. Here's what it actually does: Upload and track builds: Drop an APK, AAB, or IPA. Every upload gets ClamAV virus-scanned and SHA-256 checksomed before anything else happens. Builds move through a real status pipeline: "draft, in review, approved, published" so nothing goes out accidentally. Channels that match how teams actually work: Internal for your core team, beta for wider testing, stable when you're ready for the stores. You promote builds up the chain, and you can configure which channels require sign-off before anything moves. Approval gates: Before a build can be promoted to stable, you can require a minimum number of approvals and pass custom gates (QA passed, smoke test passed, etc.). Nobody ships to production on a whim. Distribution links with real controls: Secret link, public link, password-protected, or scoped to a specific tester list. Set expiry dates. Set max download counts. Revoke any link instantly. Android builds get a QR code on the install page so testers can scan directly from their phones. Tester feedback built in: Testers can leave a rating and written notes right from the install page. You see it all in one inbox. Analytics per build: Page views, downloads, unique downloaders, daily trend, approval latency, time to publish. Not vanity metrics... the things that actually tell you if a build is moving through your pipeline or stuck. CI integration: Scoped tokens for your build pipeline ingest builds automatically, promote from CI, read release state. No manual uploads from your laptop. Webhooks: Fire events to your own systems when a release is published, promoted, or approved. This isn't competing with the Play Store or App Store. It's the missing piece before you get there the same thing Firebase App Distribution does, but inside the platform you're already deploying on. Available now on @StackshiftCloud.

Shipped a web terminal for @StackshiftCloud this week, and I want to break down what actually went into it because the terminal itself was the easy part. Opening a shell in the browser is maybe 20% of the work. You connect a websocket to the node, attach to the running container, stream it back. Databases too… psql, mysql, redis-cli, already wired up with the right credentials so you don't go digging for them. No SSH keys, no jump box, no copy-pasting connection strings. The other 80% was the question every team hits eventually: who's allowed to touch production, and can you prove what they did? So that's where the real work went. Owners and admins get full access. People you invite get a sensible default and have to be granted more no guessing about what someone can reach. Anything running in production asks for a reason before it opens, and the session gets recorded. You can replay it later, keystroke by keystroke, like a screen recording of the shell. If a teammate needs prod access they don't have, they request it, someone approves it, and that approval is tied to that one specific session not a blanket "you're an admin now." You also get two ways in: attach to the live container, or spin up a throwaway one from your release image when you just want to poke around without touching what's serving traffic. Then the things you don't think about until you need them “runbooks” for the tasks you run over and over, one-off commands, file upload and download, recordings that clean themselves up on a schedule so storage doesn't quietly balloon. Every prod session asks for a reason and gets recorded. Team members can't just walk into a production container they request access, someone approves it, and the whole thing is being recorded. (literally, you can replay the session later) The lesson I keep relearning: the feature is the guardrails. A shell is a shell. What makes it safe to hand to a real team is everything you build around it, so people can move fast without being one typo away from a bad day.

Have you tried @StackshiftCloud Mail OTP sdk today? No separate email service. No custom OTP table. No code expiry logic to rebuild again. No delivery tracking hacks. Just send, verify, and keep building.

But this thing hard sha to implement. Plus additional server bill because of iOS. 🥲

🚀🚀

@_TechCyborg @_fusionTech Hi, please send a DM let’s get this sorted.

@_fusionTech Hi Jesse. Nice work you did on @stackshiftCloud, clean execution, I must say! I have some feedback though. On a fresh install, it fails on initial deployment, docker daemon disabled after installation for whatever reason too. I can share you some logs if that could help.

🚀🚀

@StackshiftCloud Thank you 🔥🔥

Hey guys 👋🏾 Just launched AfroLaunch - a directory for African startups 🌍 So many incredible apps are being built across Africa but barely getting visibility. I built AfroLaunch to change that - one place to discover, explore, and support African startups. 🏆 Startups get ranked weekly 📂 Browse by category & country 🔗 Find your next favorite product If you have a startup, drop the link in the comment below👇🏾 We've got just 2 launch spots left this week, and I'll help you get listed. 🔗 afrolaunch,ng

@mikailhamzat This is looking great, Chief. 🚀🚀

**afrolaunch.com

Earlier today, I launched AfroLaunch to help African startups get more visibility. The response has been amazing. These startups are already on the leaderboard: 🥇 @sendbyte_ 🥈 @cportalng 🥉 @StackshiftCloud Also making moves: • @myhappr • @qservershosting • @nestuge • @De_Boothe • Schoolcare This is exactly why AfroLaunch exists. Amazing products are being built in Africa and they deserve to be seen. If you're building something, drop your startup below and join the directory. 2 spots left for this week launch. 🔗 afrolaunch,com

@_TechCyborg @_fusionTech You mean in general terms or on StackShift?

@_fusionTech @StackshiftCloud QQ: How do microVMs work?

With @StackshiftCloud Buildpack, you get faster builds and a cleaner deploy path. On a Pro plan, your app runs with a VM-backed isolation using microVMs, so you get a stronger security boundary than a shared container runtime.

@marshallpress0n @fossapay @useTipStack @brevo_official @legendsdotfun 🚀🚀

Deployment: @StackshiftCloud Payment Gateway: @fossapay Donations: @useTipStack Email: @brevo_official Startup listing: @legendsdotfun what’s missing on the list?