I kept losing time jumping between GitHub repos, AWS Console, Datadog, and internal docs. Each context switch took ~1-5 mins of searching.
So I built ToolJump: you write JavaScript code that defines how your tools relate to each other, and a browser extension surfaces those links directly in the tools.
Example: viewing a Lambda in AWS Console shows links to the source repo, logs, and docs. Or viewing a GitHub repo shows links to prod/staging URLs and infrastructure. Imagine offering a consistent view and know-how to your whole tech org.
ToolJump is open source and:
- Fully programmable (JavaScript), encode your tribal knowledge as needed
- Can consume existing data (YAML, Backstage catalogs, service catalogs)
- Open source, no SaaS, you can host it yourself
- Git-tracked configuration (reviewable, versioned)
- Works across AWS Console, GitHub and any other tools
Built this for myself, but curious if others have this problem.
I kept losing time jumping between GitHub repos, AWS Console, Datadog, and internal docs. Each context switch took ~1-5 mins of searching.
So I built ToolJump: you write JavaScript code that defines how your tools relate to each other, and a browser extension surfaces those links directly in the tools.
Example: viewing a Lambda in AWS Console shows links to the source repo, logs, and docs. Or viewing a GitHub repo shows links to prod/staging URLs and infrastructure. Imagine offering a consistent view and know-how to your whole tech org.
ToolJump is open source and: - Fully programmable (JavaScript), encode your tribal knowledge as needed - Can consume existing data (YAML, Backstage catalogs, service catalogs) - Open source, no SaaS, you can host it yourself - Git-tracked configuration (reviewable, versioned) - Works across AWS Console, GitHub and any other tools
Built this for myself, but curious if others have this problem.
YT: https://youtu.be/6X2dpxCxCfA