Start without an existing frontend
There was no console or admin template to extend. The interface and its components had to be built from the first screen, around the security product rather than an off-the-shelf dashboard.
Case study / CybersecurityDope Security
Building the web console for a cybersecurity product.
Dope Security needed a custom console built from the ground up. Steinn Labs joined as its founding frontend team, built the entire React web console and contributed to part of the backend. Over more than a year, we worked with the product through to go-to-market and handed over a mature codebase its own engineers could extend.
- Our role
- Founding frontend team
- Engagement
- More than a year
- Scope
- Full console + backend contribution
- Outcome
- Mature product taken to market
01 / The assignment
A console built for daily security operations.
The console brings together scanner status, scan results, history and notifications. These are connected workflows: a customer needs to move from an overview of their devices to the detail behind a particular scan without losing context.
The assignment was broader than building individual screens. It meant establishing the frontend, creating a custom interface, delivering as priorities changed and leaving the client with a product they could continue developing themselves.
Deliver as the product changed
Requirements evolved as Dope Security prepared to take the product to market. The team had to accommodate changing priorities, including changes within a sprint, while maintaining delivery commitments.
Make ownership transferable
The final codebase could not depend on its original authors. Clean code, documentation and the ability for Dope Security's engineers to extend it were central to the handover.
02 / Product scope
From fleet status to the detail behind a scan.
Steinn built every screen of the custom console. These supplied product images show the breadth of the interface, from operational lists to investigation views and notifications.
Scanner fleet
A fleet-level view brings devices and their status together. Customers can inspect the list before moving into the detail of a particular scanner.
Scan detail and history
The scanner detail view puts the latest scan, verdict, infection information and prior scans in context, alongside the fleet list.
Notifications and integrations
Notifications and integration screens sit within the same console. The documented scope also includes activity logs and access control.
03 / Engineering
A custom frontend, with a maintainable foundation.
The client case study confirms React and a partial backend contribution. The frontend tools below come from the project stack already published on this site.
React · TypeScript
React application
React is the confirmed foundation of the custom console. The published project stack also lists TypeScript for the frontend codebase. The scope covers the whole web console rather than a standalone dashboard or a collection of disconnected pages.
Storybook · Tailwind CSS
Component development
The published engineering stack describes a component-driven interface, with components developed and reviewed in Storybook and styled with Tailwind CSS. This gives the team a defined place to work on the interface's reusable parts.
Vite · Vitest
Build and unit testing
Vite handles the frontend build and Vitest is listed for component unit testing. These describe the tools used, not a claim about test coverage, performance benchmarks or security certification.
Frontend and service delivery
Backend contribution
Steinn also built part of the backend alongside the console, so the interface and the services behind it could ship together. The supplied case study does not name the backend stack or claim that Steinn built the entire backend.
04 / Delivery and handover
Founding-team responsibility. Client-owned code.
For an enterprise evaluating an engineering partner, the question is not only what shipped. It is whether the team can deliver predictably and leave work that internal engineers can maintain.
- 01
Establish the frontend
Take founding-team responsibility for the console, starting with a fully custom React interface rather than adapting a prebuilt admin template.
- 02
Build out the product workflows
Extend the console across fleet visibility, scan detail and history, notifications, integrations, activity logs and access control, with backend contribution alongside it.
- 03
Keep delivery dependable
Work through shifting product priorities. The client's engineering lead explicitly confirms on-time delivery, including when priorities changed mid-sprint.
- 04
Hand over for continued development
Deliver a mature product and a clean, well-documented codebase. The client confirms that its own team could understand and extend the work.
The client's assessment
“They built our entire frontend web console, the face of our product. Delivery was always on time, even when we shifted priorities mid-sprint. The codebase is clean, well-documented, and easy for our team to extend. I recommend them without hesitation.”
05 / Documented outcomes
A product shipped, and a team ready to take it forward.
A complete console taken to market
The engagement ran from the first frontend screen through to a mature product and go-to-market, over more than a year.
Delivery the client could rely on
Dope Security's engineering lead reports that delivery remained on time despite changing priorities.
A codebase the client could own
The client's endorsement specifically calls out clean code, documentation and ease of extension by its own engineers.
The supplied case study documents delivery, product scope and handover. It does not provide quantified adoption, performance or security results.
Work with Steinn
Need a team to build
your product console?
Talk to us about your interface, engineering requirements and handover needs.