Amika
Day 28 after signup
Amika changelog: GitHub Actions, bare-metal machines and macOS VMs
Why it works
- Lead with the most substantial update, then explain its setup and practical use cases before listing smaller additions.
- Keep the changelog grounded in a founder’s conversational voice, with a direct link for readers who want implementation details.
- Close with a brief roadmap preview and a specific invitation for readers to share useful input.
How it is built
- Personal greeting and refresher
- Featured capability announcement
- Use cases and benefits
Email copy
Hi, Dylan here from Amika. A refresher: Amika connects your existing compute on one private network, and lets you make VMs across them. Quick update on what we shipped last week. You can now run GitHub Actions jobs on your own hardware by changing one line: runs-on: [amika, amika.host.<hostname>] Each job gets a fresh rig (a VM) on your machine. Steps, secrets, logs, and PR checks stay in GitHub. It's useful if you want to stop paying per-minute for hosted runners, need your own Macs or GPUs for builds, or want to keep a failed job's machine around so you or an agent can debug it. Also new: Bare-metal rigs: connect your machines directly to your Amika private network, without spinning up VMs on them. macOS VMs: run up to 2 macOS VMs on any Mac you connect. Full changelog with setup steps: https://www.amika.dev Coming up next A sandbox router. Connect your existing cloud accounts or sandbox providers to Amika. Then use one interface to create and control your VMs, and network them together. If you have any preferred cloud or sandbox providers, please let me know! Thanks, Dylan Mikus co-founder @ amika.dev Fixpoint, Inc. (Amika), 169 Madison Ave STE 11506, New York, NY 10016 You're getting this because you signed up for Amika. Unsubscribe