Case StudyHow Socure Shipped 348 Documentation Updates in 7 Weeks with EkLine

Socure, a global leader in identity verification and fraud prevention, leverages EkLine, an AI-native documentation platform for engineering teams, to turn its code changes, customer questions, and product releases into accurate, current documentation across its entire product line. In seven weeks, Socure was able to ship documentation equivalent to about six months of documentation work with the help of EkLine.

The results

In seven weeks on EkLine, Socure delivered 348 documentation updates live, across 3,026 files. One technical writer reviewed and shipped all of it.

A documentation update like these typically takes multiple engineers or technical writers to research, write, and review. At that rate, the 348 updates Socure shipped represent more than 1,000 hours of documentation work, about six months of full-time effort, delivered in seven weeks.

One technical writer is now managing an entire army of AI agents, continuously improving documentation quality, accuracy, and discoverability. Docs are now updated automatically to match the product velocity. I would have needed to hire a big team of technical writers without EkLine

Why Socure needed documentation that could keep up

For Socure, the docs are a very critical part of the product. When an external developer hits an out-of-date guide, it slows down the time to go live. Up-to-date and accurate docs help customers go live faster. With new features, API changes, SDK updates, it became extremely hard for Socure to manage the docs with one technical writer. Furthermore, there were four different Documentation repos being managed at Socure as there were two platforms catering to both commercial and public sector. Socure did not want to slow the product down, and it did not want to hire a big team of writers to keep up with the velocity of the product team.

Peter Schwarck leads documentation at Socure, and one person cannot keep up with all the product changes manually. No one can read every pull request, every API change, and every SDK release across several products and two editions, and write accurate docs for all of it before the next change lands. There are not enough hours in the week. Documentation became a top priority for the leadership due to below concerns.

• Drift. With rapid code changes every day, the docs will fall behind product releases
• Hidden gaps. Finding what documentation was missing meant checking the code against the docs line by line, which one person would never have the time to do.

The real value from EkLine is uncovering the unknown gaps in documentation that we would have never had time to find manually.

How EkLine helped Socure transform its Docs Platform by directly integrating with Github and other sources

On EkLine, Peter builds and runs multiple AI agents that learn how Socure's docs are set up. Peter's role has now evolved into managing AI Agents instead of manually creating or editing the docs. EkLine has significantly increased the impact of one Technical Writer by providing multiple agents that are working round the clock to fix documentation gaps. Everything that should change a doc, a code change, a customer question, or a release, comes into EkLine. The agents work in parallel to identify any gaps and create PRs, significantly increasing the volume of doc changes every week.

EkLine reads engineering work as it happens

EkLine watches the pull requests engineers merge and reads the actual code, going deeper than the PR summary. EkLine rates each change by how sure it is. If it is sure, it opens a doc update on its own. If it is not, it leaves a note for a person to check. A second agent looks at the week's merges and drafts the updates that should follow. Because EkLine reads the code, it catches errors a quick read would miss: a field with the wrong type, an example missing some fields, a code sample that no longer matches the SDK.

EkLine keeps both editions in sync

Keeping a commercial and a public-sector edition in sync used to mean making every change twice and hoping nothing was missed. Now, when a change lands on one side, an EkLine agent suggests the matching update on the other, so the two editions stay in sync without a tedious manual process.

EkLine learns from real customer questions

EkLine also looks at where customers get stuck due to documentation gaps. From integration with various customer support tools, EkLine reads the questions customers keep asking and turns the common ones into docs. The docs get better with every customer question, saving crucial time from the support team.

One writer, a system of agents

The biggest change is in Peter's role. He used to write every page by hand, including all the small, repeated fixes that ate up his time. Now he sets up multiple agents, points them at the right sources, and reviews what they send back. His role changed from writing the docs to running the agents that write docs at a scale one person could never reach alone.

What results did Socure see after implementing EkLine?

In seven weeks, Socure shipped 348 documentation updates, work that would have taken several months. The reach matters as much as the speed. Managing documentation across Socure with only one technical writer is no longer a concern. Because EkLine is accessible across Socure, even product managers and engineers are updating docs themselves. The Technical Writing team is no longer a bottleneck but a multiplier with EkLine.

We're now seeing nearly 10x more documentation PRs being raised compared to our previous monthly average with EkLine. In the age of AI, Docs are very critical as Developer Experience shifts to Agentic Experience.

Harish points to a bigger change too. Socure's docs went from a static site to a live loop: pull requests, API changes, release notes, and customer questions all feed back into the docs and keep them current. Next, Socure plans to roll EkLine out to more teams and cover a wider product surface area, freeing up time from teams to focus on more strategic work

About Socure

Socure is global leader in identity verification and fraud prevention for enterprise and public-sector organizations

Frequently asked questions

What did Socure achieve with EkLine?

Socure shipped 348 documentation updates live across 3,026 files in seven weeks, the equivalent of about six months of full-time documentation work, with one technical writer and no added headcount.

What is EkLine?

EkLine is an AI-native documentation platform for engineering teams. It integrates with GitHub, Slack, and multiple customer support tools to turn code changes, customer questions, and product releases into accurate, current documentation.

How does EkLine keep documentation accurate?

EkLine reads the source code directly and grades each pull request by confidence, raising documentation updates for high-confidence changes and flagging the rest for a human. Another EkLine agent analyzes customer questions from Slack and support channels and updates the docs to reduce the number of questions from customers.

Built with EkLine, the AI-native documentation platform for engineering teams.