Worktwin is built in Bergen, Norway, by one person who wanted his own tools to do the work.
Who is behind it
Kristoffer Berg — founder, and for now the whole team. Fullstack developer and product leader, based in Bergen, Norway. He builds Worktwin alongside two other products, and runs it against his own Google Drive, Slack and GitHub before asking anyone else to connect theirs.
Links: github.com/0xksure · x.com/0xksure · medium.com/@0xksure
Contact: [email protected] — a real inbox, answered by the person above.
Why it exists
Most tools that promise automation want you to describe your work in their language: a canvas of boxes, a rules engine, a queue of triggers. Worktwin starts from the sentence you would say to a colleague. You connect the tools you already pay for, describe the job once, and every run is timed, priced, and written down.
The company is small on purpose. There is no support tier, no sales team, and no account manager between you and the person who wrote the code. When something breaks, you are talking to him.
What that means for your data
Connecting a tool to Worktwin means handing over access to real work. That deserves a straight answer rather than a badge. Two things are true today, and both are written down in full:
- Every write an agent makes can be gated behind your approval, per integration.
- Every run keeps a receipt: what it did, which tools it touched, what it cost.
Read the Privacy Policy for what we store and who processes it, and the Terms for what we promise and what we don't.
Where it is
Worktwin is operated from Bergen, Norway. It is early-stage software run by an individual developer, not an incorporated company with a support organisation behind it. If that matters for your procurement, say so before you connect anything and you will get a straight answer about where things stand.