Specialized software, built to hold up in the real world.
We design the experience and build the whole system: interface, backend, data, integrations, infrastructure, and deployment. From a custom landing page to a platform, a visual editor, or an IoT product.
Scope agreed in writing before we start, and the project handed over in your name.
The services in this track
- 01
Custom landing pages
No templates. Your competitor bought the same one, and your customers have already seen it.
One page, up to six sections, designed and built from scratch for your brand. Fixed price, two rounds of revisions, and a strategy session for your business included.
- 02
Strategy session for your business
Most owners have no one to think this through with who isn't also selling them something.
One sitting to look at how your business actually runs, and you leave with up to three prioritized opportunities in software, automation, or AI plus one realistic next step. Fixed price, and it's included with the custom landing page.
- 03
Web platforms and applications
The product your team uses every day, not a demo that falls over the moment a second user shows up.
The whole application: who gets in, what each person is allowed to touch, where the data lives, how you get paid, and what happens when something breaks at 3 a.m.
- 04
Dashboards, CRMs and business systems
Your company's CRM and dashboard, with the AI working inside the product instead of in a separate tab.
Dashboards, internal portals, custom CRMs and management modules, built on data that today sits in five different places. This is where both Solaru tracks end up as a single product.
- 05
Visual editors and interactive canvases
Anyone can draw on a canvas. The hard part is making undo work every single time.
Canvases where people drag, rotate, group and export: product configurators, image editors, visual builders. It's the house specialty, and we run one of our own.
- 06
Mobile apps (iOS & Android)
A real app on both stores, not your website wearing an app icon.
iPhone and Android development end to end: the first screen, the backend it talks to, and a store listing that goes out under your name.
- 07
IoT, firmware & connected products
A connected product doesn't break at the sensor or the app. It breaks in the gap between them.
Devices that measure, report, and can be controlled from anywhere: firmware, sensors, cloud, dashboard, and remote updates.
- 08
Production control with ERP and MES
The plant produces every day. The numbers, how much, at what cost, with how much waste, arrive a week later. If they arrive.
Software to run production: orders, inventory, costs, traceability, and the shop floor reporting live. And more broadly, any development that removes manual steps from an industrial process.
- 09
Backend, APIs, MCP & infrastructure
Most projects don't break on the screen: they break when it's time to plug them into what you already run.
Databases, servers, jobs that run unattended, and the connections between your systems, including the MCP servers that let an AI agent query your data with permissions and a paper trail.
- 10
Product design (UI/UX)
The way a tool gets used isn't added at the end: it decides what gets built in the first place.
Interviews, flows, a clickable prototype, the final screens, and the visual system they're built from. Available on its own, and baked into everything we build.
Every project is quoted by scope, agreed in writing before we start. The custom landing page and the strategy session are the two with a fixed price.
How we work
Before building, we turn the problem into a clear specification: what the system must do, what data it uses, where its limits are, how it's validated, and what finished means. It's called spec-driven development, and it's what makes a result repeatable.
- 01
Understand the business
Who's going to use this, what for, and what happens today without it. We talk to the people doing the work, not just the person paying for it.
- Conversations with whoever opens it daily
- The problem underneath the requested feature
- What exists today and what can be reused
- 02
Write the spec
What the system must do, what data it uses, where its limits are, how it gets validated, and what finished means. Before any code.
- Closed scope: what's in and what's out
- The data and where it comes from
- What is explicitly excluded
- 03
Flows and acceptance criteria
Every screen and every process with its definition of “done” written up front. A criterion defined after the build is an opinion, not a criterion.
- Whole journeys, not isolated screens
- Empty, loading, and error states
- What counts as finished, in writing
- 04
Design and prototype
A prototype you can click through before a single line of code exists. If the flow doesn't work in gray, color won't save it.
- Information architecture and flows
- A prototype you can walk through and test
- The visual system everything else is built from
- 05
Build in increments
Every week there's something working at a link you can open. No three months of silence waiting for a result.
- Small, verifiable releases
- A separate staging environment from day one
- Anything out of scope gets quoted, not argued about
- 06
Test with real data
Yours, not made-up names. It's where whatever the design failed to anticipate shows up.
- Real edge cases and real volumes
- Checked on actual devices, not just a simulator
- Fixes before launch, not after
- 07
Deploy
With a domain, backups, monitoring, and the rollback plan written before we ship, not improvised the day something breaks.
- Production and staging, kept apart
- Alerts and error logging
- Rollback plan ready in advance
- 08
Measure, document, hand over
The project, the accounts, and the keys in your name, with the manuals for how it runs and how it's put together.
- Analytics working from day one
- Operations and architecture documentation
- A recorded handover session with your team
Development agents take part in the process, but they always work against specifications, standards, and human review.
Included in everything
Responsive, accessibility, deployment, and handover aren't surprise line items at the end of a project. They're standards of what we build, unless the written scope says otherwise.
Actually responsive
Checked from 320 px up to a wide monitor, on real phones and machines, not just in a simulator. It isn't a phase at the end: it's a condition of every screen we draw.
Accessibility
Keyboard operable, with visible focus, contrast that meets the WCAG AA standard, and animations that settle down for anyone who asked their machine for less motion. Included, never billed separately.
Deployment and monitoring
Live on the internet with its domain, a staging environment separate from what your customers see, tested backups, and an alert that reaches you before your customer notices.
Handed over in your name
The project, the accounts, and the keys end up in your name, with manuals and a session with your team. If you decide to work with someone else tomorrow, you don't have to ask us for anything.
Or is yours the other one?
AI implementation for businesses
We look at how your company operates, design the architecture, and leave agents, skills, and AI workflows running inside the tools you already use.
What do you want to build?
Tell us the case, what you have today, what you need, and by when, and we'll tell you the best place to start. Before we quote a price, we put in writing what's in and what's out.
We reply within one business day