Vihren is open-source Go tooling for teams that already use Temporal as the durable spine of their systems. The best fit is a production Go/Temporal team with long-running workflows that wait on people, call external systems, recover from partial failures, or are starting to carry brittle LLM-assisted steps.
Good fit
- You already run Temporal in Go, or you are actively moving a Go service onto Temporal.
- Your workflow spans hours, days, or weeks and has human waits, signals, external APIs, retries, or audit requirements.
- You want direct integration help where the reusable parts harden the open-source Vihren platform instead of becoming a private fork.
Available today
- Vihren Codegen generates typed activity proxies, workflow clients, and worker registration from ordinary Go code.
- Embedded Temporal supports examples, demos, local development, and single-process tools.
- Generated code stays close to the native Temporal SDK. Vihren removes stringly-typed plumbing; it does not hide Temporal.
Integration work
The work is intentionally narrow: apply Vihren to a real Go/Temporal workflow, remove boilerplate, make the failure boundaries explicit, and turn reusable gaps into platform improvements. Some edges may be hand-held before they are fully productized, especially production deployment details, workflow-specific testing shape, and observability around long-running automation.
The right engagement leaves you with working code in your repository and leaves Vihren with a better general-purpose path for the next Go/Temporal team.
Not the focus
Vihren is not a Temporal replacement, a hosted workflow platform, a no-code builder, or an open-ended consulting shop for unrelated systems. If the work does not make the open-source platform better, it is probably not a fit.
Contact
Email contact@vihren.dev with a short description of your Temporal workflow, the Go service it lives in, and the failure mode or boilerplate that is slowing the team down.