Contact
Tell us which build lane is hurting.
There is no form on this page. Email reaches the same small team directly, and a specific message gets a specific answer, including, sometimes, that Horu is not the right tool for the problem you described.
Early access
What happens after you send it.
We onboard a small number of studios at a time, because early reports are read by the people who wrote the tool and that does not scale. Here is the whole process. There is no queue position, no counter, and nothing to share on social media.
Studio context
Seven things that make our answer useful.
The mailto link above is pre-filled with exactly these fields, so you can answer them in your own mail client without filling in a web form that emails us anyway.
The more specific your production context, the faster we can say whether the current implementation helps, or which phase of the roadmap you should be waiting for.
- Game engine and version, and whether the project has a custom build pipeline on top of it
- Current CI stack and repository hosting model
- Which single build lane causes the most pain, and what it is used for: nightly, PR validation, store release
- Average pipeline duration and the highest-friction stage inside it
- How cache behaviour is currently handled, and whether anyone can explain a miss
- Security, compliance or audit constraints that a build tool would have to respect
- Target outcome: faster builds, fewer release risks, lower CI cost, or stronger evidence for governance
Channels
One address, no form in between.
Everything reaches the same people. Include the technical detail in the first message; it saves a round trip.
Routing
Where each kind of message should go.
One address handles everything, so the useful part is your subject line.
| Topic | Where | Include |
|---|---|---|
| Horu CLI early access | Email, subject Horu early access request |
The seven studio-context points above. |
| Horu CI evaluation | Email, subject Horu CI evaluation |
Your current orchestrator, runner fleet, platform hardware constraints, and what you would need to move. Read the status split first. |
| Something is wrong on this site | Email, subject Website correction |
The page and the claim. |
| Recruiting | See the careers page for what makes a speculative message useful. | |
| Group and partnership enquiries | Email, or HoruSphere Group | Which company in the group your enquiry concerns. |
Company
Who you are dealing with.
- company
- HoruSphere Systems, a HoruSphere Group company.
- group
- horusphere.com
What a vague message gets
A short reply asking for the seven points above. Not out of process pedantry: without an engine version, a CI stack and a named build lane, any answer we gave would be generic marketing, and you would be right to ignore it.
One lane. One config file. One comparison.
If that produces nothing worth keeping, we would genuinely rather find out now, and so would you.