Building and maintaining cybersecurity integrations.

Synqly is the connected platform for security and IT operations, providing a unified API that allows security software vendors to deliver integrations across the full ecosystem of SIEMs, EDR platforms, ticketing systems, vulnerability scanners, and asset management tools — without rebuilding connectors for each one.

{ How we made it happen }

Problem

  • Synqly's core product is a unified API that eliminates a fundamental bottleneck in the cybersecurity industry: the need for every security software vendor to build and maintain separate integrations for every tool their customers use. The average enterprise security team manages more than 75 security products. For the vendors serving those teams, every new customer environment arrives with a different mix of SIEMs, EDR platforms, ticketing systems, and vulnerability scanners — each with its own API behavior, data model, and rate limits. Synqly's platform normalizes all of it into a consistent interface, so vendors integrate once and gain access to an entire ecosystem. The engineering challenge behind that product is relentless. Building and maintaining individual provider connectors is specialized, detail-intensive work: understanding how each vendor's API actually behaves in production, mapping provider-specific fields to normalized OCSF schemas, accounting for undocumented edge cases, and keeping pace with API changes that vendors often make without announcement. The integration backlog at a fast-growing platform like Synqly never gets shorter — new providers are always in demand, and existing ones require continuous maintenance. When Synqly approached Admios, they needed experienced Go engineers who could work autonomously in a production codebase, ramp up quickly without a formal onboarding program, and deliver quality integrations from the start. Building out a full internal team in San Jose at the pace their roadmap required wasn't viable. They needed a trusted engineering partner that could put capable engineers on the work immediately — and scale the team as the roadmap expanded.

Approach

  • Admios embedded two Go engineers with Synqly in January 2025, working directly with the integration team lead and senior architects on the Synqly side. Both engineers joined the live pipeline immediately — taking on real provider work within their first weeks, operating as fully embedded members of the integration team rather than as external contractors with a defined deliverable list. Work has spanned the full range of integration categories in the Synqly ecosystem. An engineer focused on the EDR and asset management categories implemented new provider connectors — including ESET for endpoint detection and response — and worked on filtering capabilities for vulnerability findings endpoints and bulk device management. A second engineer took ownership of the ticketing integration category, building normalizations across providers including Jira, ServiceNow, and Rapid7, and leading a proposal for SIEM and major indexing engine integration. All work is built in Go against Synqly's domain-driven, pipeline-based architecture and normalized to OCSF schema standards. The team expanded to four engineers by early 2026. Synqly provides enterprise Cursor licenses with Claude as the underlying model, and the Admios engineers operate within that same toolchain — using AI-assisted workflows for scaffolding new provider integrations, generating Postman workspaces from vendor API documentation, and running pre-push reviews against the CI/CD spec before code reaches the review queue.

Results

  • The Admios team has contributed production integrations across every major category in the Synqly ecosystem — EDR, ticketing, asset management, vulnerability management, and SIEM. That breadth matters directly to Synqly's business: the platform's value to its customers scales with the number and reliability of integrations it can offer. Every connector built is a capability that Synqly can sell, and that its customers can activate without any additional engineering effort of their own. The engagement has grown in step with Synqly's expansion. Engineers from the original placement remain active on the account, and the institutional knowledge they carry of the codebase, the providers, and the Synqly team's engineering standards compounds meaningfully over time.

{ Overview }

Industry
Cybersecurity / Integration Platform
Company Size
Early-stage startup
Dev Team Size
4 engineers

{ Key Results }

  • The Admios team has grown to four engineers embedded on the account — a consistent expansion that reflects delivery quality and deepening trust across a complex, production-grade integration codebase.
  • The Admios team has delivered production provider integrations across EDR, ticketing, asset management, vulnerability management, and SIEM categories. This expands the set of connections Synqly can offer to its customers without additional engineering effort on their end.
  • An Admios engineer is leading the migration of Synqly's full ticketing integration suite to the platform's updated pipeline architecture — a high-complexity, cross-vendor effort touching every major ticketing provider in the ecosystem, including Jira, ServiceNow, and Rapid7.
  • With close to 100 integration partners and a presence at RSA Conference 2026 as the first AI-enabled unified API for security integrations, Synqly is scaling fast — and the Admios team remains embedded and active at the platform's most consequential growth stage.

{ Stack Used }

No items found.