Next.js developers who shipped a startup's integration catalogue
How a YC-backed product-tooling startup used Lyra's Next.js developers to build and publish integrations with Jira, Azure DevOps, Raycast, Microsoft and Canva, plus a Chrome extension, in about three months.
A YC-backed product-tooling startup needed integrations with the work tools its users already live in. Lyra's Next.js developers built an integration layer and shipped apps for Jira, Azure DevOps, Raycast, Microsoft and Canva, plus a Chrome extension, in about three months. A year later, the Azure DevOps integration is still in daily customer use.
At a glance
- Client: YC-backed startup that turns work context, like tickets, into product prototypes
- Need: a catalogue of third-party integrations, built to each vendor's standards
- Team: 3 engineers, about three months
- Stack: Next.js, TypeScript, OAuth, vendor app platforms, Chrome extensions
The problem
The product works by pulling context from tools like issue trackers. Every integration has its own auth model, data rules and marketplace review, and the founding team wanted to spend its time on the core product, not on vendor compliance checklists.
What Lyra's developers built
An integration layer in Next.js that handles each vendor's OAuth and session auth and passes context to the client's main Java and Kotlin backend.
A Jira and Atlassian app with correct OAuth scopes and Atlassian's compliance requirements, including weekly automated reporting of stored personal data.
More integrations: Azure DevOps (published to Microsoft's marketplace), Raycast, Microsoft and Canva, plus a Chrome extension. Each went through the client's own review.
Results
- Five integrations and a Chrome extension shipped in about three months.
- Marketplace listings approved under each vendor's rules.
- Still in customer use a year later, with no rebuild needed.
Hiring Next.js developers: freelancer, software agency or embedded team?
A freelancer can build one integration. A software agency can quote the lot as a project. This client needed developers who followed its code review and conventions, so each integration fitted the product and could be maintained by its own team afterwards. Lyra's Next.js developers worked inside the client's repos and reviews and left code the in-house team still runs.
Read more: What is a forward deployed engineer?
Frequently asked questions
