Kelt made major progress toward production-ready iOS and Android previews. The M5 hosts was hardened, four isolated iOS preview slots were validated per M5, and M5-first/M4-fallback scheduling was added for our legacy M4 systems. Audits uncovered costly AWS/Vercel video routing, leading to a new datacenter-direct media design. The colo was confirmed to support 1 Gbps connectivity, low-cost bandwidth, inbound 443, scalable power, and the new HPE server will support owned Android compute.
Completed Today
M5 Golden Image and deployment to Dev Environment. Ordered the DL385 Dual 64-Core Server.
Today we met with Millennium Systems LLC to establish a working relationship for our Mac Studio M5 Systems. We initially benchmarked Mac Mini M4's but the return on investment wasn't adequate. They could only push 2 previews per M4 device. We upgraded to 18-core M5's with 64GB of RAM on our first 4 x Machines. But after testing we determined that our iOS previews were CPU heavy and that memory was nominal. Going forward, all of our additional M5's will be loaded with 18-Cores, 36GB of RAM, and 512GB of storage
Milestones
Worked on Engine Security, Android Preview through KVM using AWS until we get our 64 Core Epyc dual socket server.
Completed Today
Built our first Golden Image for our M5. Connected 10 x M5's via SSH for configuration.
Fixes & Improvements
Security isolation probe, tightened network configurations and prepared imaging.
Closed major pre-launch security and billing milestones. Billing/paywall and Auth hardening are production-accepted. Engine-security now has a tested customer-process isolation hotfix, migration 0177, and KVM proxy allowlist in draft PR #256. Android KVM security owns 0176/PR #252 and is finishing its final export-pin/rollback gate while fleet stays 0/0/0. M5 setup is nearly complete; tomorrow is four-slot persistence, reboot/login acceptance, then Kelt production registration.
Milestones
Engine-security hotfix is fully tested in draft PR #256 with customer-code isolation, migration 0177, secret protections, and KVM proxy allowlist.
Completed Today
Billing/paywall hardening is production-accepted, including migrations 0173/0174, Stripe webhook validation, and final staging parity.
Fixes & Improvements
Auth hardening is production-accepted with migration 0175, anonymous access blocked, signup controls enforced, and rollback verified.
Remaining Blockers
Android KVM security is in final closeout on PR #252/0176. Fleet remains safely at 0/0/0 while export pins, rollback, and CDK diff are finalized.
Engineering Next
Migration order is now locked: 0172 Store Delivery, 0173–0174 Billing, 0175 Auth, 0176 KVM, 0177 Engine-security.
Engineering Notes
M5 production-host setup is nearly complete. Remaining: clean four-slot persistent setup, real reboot/login acceptance, then register the Mac with Kelt production.
Kelt’s final pre-launch work focuses on four areas: stabilizing the Dependency Watcher so web previews restart cleanly without port conflicts, completing Hostname Safety for long project names and certificates, finishing Store Delivery’s Engine workers for iOS/Android publishing, and running a final end-to-end launch acceptance across fresh Web, iOS, Android, Expo, billing, auth, deployment, and integrations.
Milestones
We completed major Preview reliability milestones, expanded Android/Expo capacity, hardened Web Preview, fixed native cache/state issues, advanced Store Delivery to production control-plane readiness, and prepared final launch lanes.
Completed Today
Today we closed major Preview blockers, scaled Android/Expo KVM capacity, hardened Web Preview, fixed stale APK caching, advanced Store Delivery control-plane work, and prepared Hostname/Dependency Watcher next steps.
Fixes & Improvements
Today we fixed KVM scaling, Android false Ready/idle/stale APK issues, Expo log spam and phantom Web rows, Web Server Actions/recovery, multi-tab Stop, and advanced Store Delivery.
Engineering Next
Next: finish Preview, close Dependency Watcher, deploy Hostname Safety, complete Store Delivery Engine execution, then run the final fresh-project launch acceptance across Kelt.
Today we've crossed a major milestone. AI Build Credit consumption on the initial demo build is done! And we've added a newsletter/subscriber feature as well as a comment box for you to offer feedback and recommendations that our competition isn't offering. We want our users to be happy.
Completed Today
Added the Newsletter and comment box. And we finished AI Build Credits consumption on initial demo from home page.
Engineering Next
About to start wrapping up Connected Accounts
Product Requests
What should Kelt build next?
We're building Kelt Forge for people who want an AI developer that can actually build, deploy and manage real applications. Tell us what's missing from the tools you use today.