veyla
The Sails that Shape the Wind
Origin: from the constellation Vela — Latin for "sails"
In ancient navigation, the sails were both art and engineering — geometry meeting intuition. "Veyla" takes its name from Vela, the constellation representing the sails of the ship Argo that carried explorers through uncharted seas.
Like its namesake, Veyla is a tool for those who design with motion in mind — it doesn't just capture direction; it creates it. Every element and link in Veyla mirrors the quiet discipline of tensioned canvas catching invisible forces and turning them into forward movement.
Design that catches the wind.
veyla voyage
Press Space or click to start · Arrow keys to steer · ↑ to shoot · ↓ to calmHigh Score Challenge
Screenshot your high score and send it to us on LinkedIn. Top score each month-ish wins a prize.
Offer null where prohibited.
Leaderboard
Join the Team
Or whatever this is called at the moment.
We're a small team based in the south-central US. West of the mid-west and east of the west coast. We build tools for engineers who are tired of spending more time filling out documents than actually engineering things. If that sentence made you involuntarily sigh, you might be our kind of people.
Proximity matters. Not in a "mandatory fun" way, but in a "we occasionally need to argue about architecture in the same time zone" way. Remote-friendly, but being within a reasonable drive of the team is a real plus.
Benefits are null. We're not going to pretend there's a ping pong
table...but there's also no unlimited PTO that nobody actually takes. What does exist: interesting problems,
an absurd amount of autonomy, and the quiet satisfaction of making bureaucracy slightly less terrible.
How this actually works
Full-time positions exist but are rare. Most of the team are engineers in disciplines that need tools like veyla. They build and contribute alongside their real jobs because they've lived the pain and want it fixed. We want tools to work for us, not the other way around.
The most common way in? You want Veyla to connect to a tool we don't support yet or you want to add a new feature. You help us write the spec, integration, and/orders the API. Somewhere in the pull requests and the late-night Slack threads, we realize we like working together. That's genuinely how we find most people. No whiteboard interviews or "where do you see yourself in five years". Build something useful with us and see if we're better off for it.
The mission
We're fighting document-based, bureaucratically heavy, pointless processes that have somehow convinced entire industries they're "necessary." We're trying to bring efficiency back to engineering...the actual discipline of solving complex, worthwhile problems.
If you're up for it, reach out. We don't have a careers page because, frankly, that feels like a homework assignment and we don't have anyone with HR in their title anyway.