Running customer code safely inside InDoc EDGE

InDoc EDGE is Mikrocop’s platform for document management and process automation in regulated sectors. We built the service that runs its customers’ own code, delivered three modules and then joined its core team.

Used by

InDoc EDGE in the browser: document folders, a tagged file list and a roadmap preview pane
Industry
Document management & process automation
Engagement
Projects, Teams and Specialists
Scope
Backend, frontend, architecture, testing, documentation
Timeline
June 2024 to September 2026, 4 engineers

The situation

A roadmap larger than the team available to build it

InDoc EDGE manages documents and business processes for enterprises in regulated sectors, from capture and approval to electronic signing and long-term archiving. Its customers include OTP banka, Luka Koper and GLS.

Mikrocop’s roadmap held more work than its development team could deliver within the release schedule. Complete modules were planned with no one free to build them, and a new Scripting Sandbox needed expertise the in-house team did not have.

The sandbox was the hardest part. Customers write C# scripts in the process editor to add their own calculations and rules, so the platform has to run code it does not control. In the previous environment, a script could stop a sandbox instance or reach the machine it ran on.

What we built

A Scripting Sandbox we owned end to end

The sandbox was a fixed-price project, delivered on the agreed date. We owned its specification, architecture, development, testing and documentation.

It is a separate .NET service that InDoc EDGE calls over gRPC. Each script runs in its own isolated Linux process, with limited computing resources and no access to the host machine. More instances can be added as load grows, and they can be shared between InDoc EDGE deployments, with load balancing on the calling side. Redis caches compiled scripts, and a fallback to the legacy sandbox covered the transition.

We also delivered three modules independently, refining tickets with Mikrocop’s product owners and estimating with its technical team. For Document Signing, we rewrote Mikrocop’s legacy library for creating and verifying digital signatures in full, on modern design patterns and current APIs. The External API work moved more configuration into InDoc EDGE’s own settings and added token-based authentication (JWT), with full backwards compatibility for integrations already in production. Bookmarks added organisation-wide bookmarks, controlled by administrators with full access control, alongside personal ones.

Inside the team

From delivering modules to building the core product

With the modules delivered, the wider roadmap still needed people. Our engineers joined Mikrocop’s core team and worked within its process, from specification to testing.

We extended the BPMN workflow engine, which models each business process, and rewrote the access control system. We traced and fixed hard defects: one in audit logging, where one customer’s failed entries could be picked up and mislabelled under another’s, and one in background jobs, where duplicate workers raced on the same records. We also helped move the frontend from the older Durandal framework to React.

On the frontend, we designed in-app back navigation that behaves like a browser’s, with fallbacks that replaced hardcoded routes, added form components for complex input and carried out the major package upgrades: React Query to v5, the deprecated MUI packages and react-i18next.

The outcome

Releases that shipped 30% more feature tickets

The releases we worked on shipped 30% more feature tickets than the releases before we joined, a record for InDoc EDGE.

The signing rewrite replaced a legacy library with one that is substantially simpler to maintain and scale. Document signing and verification became 65% faster.

The new sandbox handles 1,500 scripts per second on two instances, twice the throughput of the previous environment, and scripts can no longer stop an instance or reach the machine it runs on. After the External API changes, some client-requested integrations need up to 90% less work, and one class of custom integration no longer has to be maintained.

Outcomes

  • 1,500

    Scripts per second on two sandbox instances

    750 per instance, twice the throughput of the previous environment

  • 65%

    Faster document signing and verification

    After a full rewrite of the legacy library: 1,053ms to 363ms in benchmarks

  • 30%

    More feature tickets shipped, a record for InDoc EDGE

    In the releases we worked on, compared with releases before we joined

  • Up to 90%

    Less work on some client-requested integrations

    After the External API changes

I’m really happy with our collaboration. We’ve worked with many companies before, and Extra.dev stand out. They have a more ‘international’ approach: fast, responsive, efficient, on par with what you see in the US. Moreover, they don’t make excuses. They take ownership. They solve problems proactively, and when something goes wrong, they react and fix it. That’s a big green flag. And it’s what brings results.
Primož RupDirector of Information Technology, Mikrocop

What we shipped

  • Scripting Sandbox service, from specification to documentation
  • Isolated, resource-limited script execution that scales across instances
  • Rewritten library for creating and verifying digital signatures
  • External API configuration within InDoc EDGE settings
  • Organisation-level and personal bookmarks with access control
  • BPMN workflow engine extensions and a rewritten access control system
  • Fixes for tenant-separation and concurrency defects
  • Contribution to the frontend move from Durandal to React
  • In-app back navigation with fallbacks, replacing hardcoded routes
  • Frontend package upgrades, including React Query v5 and MUI

Built with

Back-end

  • .NET
  • ASP.NET
  • C#
  • gRPC

Data

  • SQL Server
  • Redis
  • Elasticsearch

Front-end

  • React
  • TypeScript

Platform

  • Docker Swarm
  • Isolate
  • TeamCity
  • Bitbucket

Other engagements, other constraints.

  • The Hyperice app open on a phone, beside a Hyperice massage gun

    Hyperice

    Backend rewrite for the HyperSmart app, four weeks before launch

  • Blissbook on a desktop monitor: the policy library, each policy listed with its owner, update status, jurisdiction and handbook chapter, with saved policy views alongside

    Blissbook

    AI features and core product development for HR policies

  • The PrizePicks app on a phone resting on a basketball: NBA player cards, each with a points line to pick over or under

    PrizePicks

    Architecture and development for The Esports Lab

The voices of our clients

  • Laurence CreamerCo-founder, PunkPadel
    Our booking platform is central to how we run PunkPadel, from taking payments to operating our venues. Extra.dev understood how it supports the business and strengthened it for growth. We now have a reliable system for day-to-day operations and the flexibility to expand as the business develops.
  • Luka GuboCEO, JonatanMars
    In investment services, accurate and reliable software is part of the trust clients place in us. Extra.dev understood our operations and regulatory requirements, built our new application and its supporting systems, and migrated existing client accounts from the previous platform. They have continued working with us as requirements change, bringing technical expertise grounded in an understanding of our business.
  • Sebastian GreshakeCEO, Naval Architect & Seavizor
    Extra.dev was a key part of our development efforts for over two years, contributing across various projects and consistently impressing us with their versatility and speed. Their team tackled complex desktop software, web applications and cross-platform mobile apps. Extra.dev’s “get it done” attitude and reliability meant they consistently delivered results on time.

Tell us what you’re building.

The complex, the critical, the bold. We’ll tell you how we’d ship it.