hurry is the product Attune launched with. The YC page, the Launch YC post and the open founding-engineer role still lead with it ("Faster builds, zero effort", "up to 20x faster"), and with 55 stars it is Attune's second most-starred repo. Its README has one setup step: get an API token from hurry.build. When checked twice on November 10, 2026, hurry.build returned HTTP 404. The homepage no longer mentions hurry either. So every developer who arrives from YC, GitHub or a referral, keen to try the speed-up, hits a dead end at the one step that turns interest into a user.
First action
Today, point hurry.build at an attunehq.com/hurry page that explains hurry's status and offers the self-hosted path.
How to measure it
Weekly hurry activations (tokens issued plus self-host installs)
- Now
- –
- Target
- From 0 to 10 a week
- By
- 30 days
Steps
Restore or redirect
Bring hurry.build back, or 301 it to attunehq.com/hurry.
Cofounder, Engineering 2 hours
Write the hurry page
Status, supported Rust versions and platforms, managed versus self-hosted, and a token request.
CEO 1 day
Fix the README
Point the token step at the working page; lead with self-hosting if the managed cache is paused.
Founding Software Engineer 1 hour
List hurry on the homepage
Add it next to nudge, caliper, bastion and akari.
Founding Software Engineer 1 hour
Add uptime checks
Monitor hurry.build and the token flow, with alerts to the team.
Cofounder, Engineering 1 hour
Tell past interest
Reply to open issues and anyone who emailed about rollout that sign-up works again.
CEO 1 day
Measure
Weekly tokens, self-host installs and page visits from GitHub and YC.
CEO weekly
Why it works
Within a week, make every path to hurry end somewhere that works. (1) Restore hurry.build, or redirect it to a new attunehq.com/hurry page. (2) On that page, state hurry's status honestly (alpha, Rust 1.92 and earlier, macOS ARM64 and Linux x86_64 first), give the two ways to start (request a managed-cache token, or self-host using the existing docs), and offer a short form or email for rollout help. (3) Update the README so the token step points to the working page and the self-hosting path comes first if the managed cache is paused. (4) List hurry on the homepage with the other projects. (5) Watch the page so a future outage is caught in hours, not months.
Developers rarely report a dead sign-up link; they just leave. The demand already exists in the YC directory, the launch post and the GitHub stars, so a working page turns traffic Attune already earned into users and conversations at almost no cost, and it keeps the launch product from damaging trust in the newer tools.
Ready to use
Checklisthurry front-door checklist
[ ] hurry.build loads or 301s to attunehq.com/hurry [ ] Page states status: alpha, Rust 1.92 and earlier, tier 1 platforms [ ] Two starts: request a managed-cache token, or self-host [ ] README token step points to the working page [ ] hurry listed on the attunehq.com homepage [ ] Uptime check on hurry.build and the token flow [ ] YC profile and launch post link to the same page
Risks and how to handle them
The managed cache is deliberately paused
Say so on the page and send people to self-hosting, which the repo already documents.
New users hit the Rust 1.93 limit
State the supported versions above the install command (see idea 17).
Evidence
- hurry.buildhurry.build, where the hurry README sends new users for an API token, returned HTTP 404 both times it was checked on November 10, 2026.Source
- GitHubhurry README: "Really, really fast builds"; in alpha; run hurry cargo build with an API token from hurry.build, or self-host; supports Rust 1.92 and earlier because Rust 1.93 removed a Cargo feature it relies on; 38 open issues and 6 open pull requests.Source
- Y CombinatorYC company page: one-liner "Faster builds, zero effort."; moving from cargo build to hurry cargo build can make builds "up to 20x faster"; Rust now, Docker and other languages planned; founded 2025, Spring 2025 batch, team of 3, San Francisco; the founders previously led product at Teleport and engineering at FOSSA.Source
- GitHubAttuneHQ organisation (November 10, 2026): 24 public repositories, 14 followers and no organisation bio. Stars: nudge 84, hurry 55, caliper 7, bastion 7, akari 7. bastion and akari were updated on November 9, 2026 and nudge on November 3; hurry was last updated on January 23, 2026.Source
- Your websiteHomepage (checked November 10, 2026): "Attune is an applied AI company building the future of software engineering." It lists four projects, nudge and caliper (linked to GitHub) and bastion and akari (on tunas.dev subdomains), plus two posts. Hurry is not listed, and there is no contact route, email sign-up, team, customer, pricing or careers link.Source