alawadi.cloud v0.1.0: the First Managed App Hosting Beta
Our first full platform beta is tagged: container apps, voucher billing, managed databases, private registry workflows, docs, status, support, and GitOps releases.
Today we tagged v0.1.0, the first full beta release of alawadi.cloud as a managed app hosting platform.
This is the release where the product stops being only a landing page and becomes something a founder-led beta customer can actually use: sign in, create a project, run a container app, connect deploys, redeem vouchers, inspect activity, open support tickets, and read the docs.
What shipped
The beta now includes the public website, customer portal, API, docs site, and status page as separately built and released services.
- Managed container apps with project-scoped namespaces, logs, metrics, health, restart, stop, start, delete, and deployment history.
- Google sign-in and a real customer portal at
app.alawadi.cloud. - Voucher billing with redemption, admin minting, welcome credit, transaction history, and pay-as-you-go foundations.
- Private registry workflows with GitHub Actions OIDC guidance and tenant-scoped image namespaces.
- Managed Redis, Postgres, and MySQL foundations for project services.
- Custom-domain flow using Cloudflare for SaaS, with verification and status inside the portal.
- Activity, notifications, settings, and support center so customers and operators can see what happened and respond inside the product.
- Developer docs at
docs.alawadi.cloud, including first-deploy guides, deploy API reference, billing docs, and troubleshooting. - Public status page at
status.alawadi.cloud.
What this release means
v0.1.0 is a beta, not a mass-market launch. The right next step is founder-led onboarding: sit with early users, deploy real apps with them, and watch where the platform feels sharp or confusing.
That matters more than pretending the product is finished. The core is here now: Kubernetes, TLS, GitOps, logs, registry, billing, support, and docs. The next work is evidence: live smoke tests, customer feedback, pricing discipline, and operational muscle.
What still needs evidence
We are keeping the caveats public:
- Live end-to-end smoke tests still need to be captured after each release.
- Production tenant-isolation evidence needs to be recorded for real beta workloads.
- Some operator tasks remain manual, including PITR credential sealing for managed databases.
- Billing cutover will stay explicit and auditable. No surprise charging.
Release links
- See everything that shipped in this release on the alawadi.cloud changelog.
- Start with the docs: docs.alawadi.cloud
To try the beta, open the portal at app.alawadi.cloud. If you need beta access, vouchers, or help with a first deploy, email [email protected].
The company behind alawadi.cloud
The company building an Arabic-first cloud platform, from the physical servers up to the developer experience.