Work with Vihren
Both Vihren products are early enough for real teams to shape them. We are looking for design partners, consulting engagements, and engineering contracts where the work is grounded in an actual codebase or durable workflow.
Map a real codebase with Vihren Atlas.
Atlas is a good design-partner fit if your team has a substantial automated test suite and needs better answers about runtime coupling, change impact, test evidence, architecture drift, or the context supplied to coding agents.
You bring a repository, its test and coverage constraints, and the questions your team struggles to answer. We help determine what Atlas can observe, build or import the analysis, and evaluate whether the resulting map supports real review and architecture work. Product improvements that generalize should shape Atlas rather than become a private fork.
- Which repository and languages are involved?
- How is the relevant test suite run today?
- Which review, refactoring, or architecture question is hardest to answer?
- Can coverage or derived analysis leave your environment?
Shape Vihren ADK around a real workflow.
This track is a good fit if Temporal is infrastructure for your Go application and you are adding long-running, tool-using, human-in-the-loop, or LLM-assisted behavior. Vihren ADK is a work in progress; the purpose of a partnership is to design against production constraints rather than pretend every agent primitive already exists.
You bring a workflow and its constraints. We help map it onto the current Go and Temporal foundation, identify missing reusable primitives, and contribute the general parts to Vihren ADK. The work should improve the public foundation rather than create a private framework hidden behind it.
- What does the workflow do and how long can it run?
- Where do people, tools, retries, or external systems enter the loop?
- Which failure, observability, memory, payload, or sandbox boundary is hardest?
- Which parts can become reusable open-source work?
What a first conversation is for.
The first conversation is for testing fit and defining a bounded problem. It is not a claim that installing Vihren solves a codebase or workflow automatically. If the problem fits, the next step can be a design partnership, a consulting project, or an engineering contract with explicit scope.
Contact
Email [email protected] with “Atlas” or “Vihren ADK” in the subject, a short description of the codebase or workflow, and the question or constraint you want to address.