Skip to content

Dev4me

Where off-the-shelf software reaches its limits.

Custom development, integrations and technical projects – from the circuit board to the cloud. We build the systems for which there is no product off the shelf.

Domains
Electrical engineering + computer science
Location
Grenchen, Switzerland
Entry point
Feasibility in 2 weeks

Two domains

One workshop for current and code

Most problems sit neither in the software nor in the hardware, but exactly in between. We work on both sides of the interface – which is why we do not have to guess it.

Electrical engineering

From the sensor to the assembly

Circuit design, printed circuit boards, microcontrollers, measurement, actuators and fieldbuses. We build prototypes you can touch, measure and test.

  • Circuit design & layout
  • Firmware in C/C++/Rust
  • Measurement and test rigs
  • Fieldbus & industrial protocols

Information technology

From the data point to the application

Business applications, APIs, data models, analysis and operation. So that measurements turn into decisions – traceable and maintainable.

  • Custom software & portals
  • APIs & system integration
  • Data models & analysis
  • Operation, monitoring, maintenance

Services

Six channels, one signal path

Select a channel to read the service. Each one can be commissioned on its own – in practice they usually interlock.

Select a channel to read the service

RUN TRIG'D CH1
FREQ
AMPL
TIME
DUTY

Approach

From signal to system

Technical projects rarely fail because of the code, but because of unclear assumptions. That is why we measure early and deliver in stages you can stop at.

  1. 01 Input

    Clarify

    A conversation about the problem, not about technology. At the end there is one question whose answer decides the project.

  2. 02 Calibration

    Measure

    The critical assumption is tested – with a small rig, a load test or a data analysis.

  3. 03 Clock

    Design

    Architecture, interfaces and circuit concept on two pages. Enough to put a figure on effort and risk.

  4. 04 Gain

    Build

    Implementation in short increments with working intermediate versions. You see progress, not status reports.

  5. 05 Coupling

    Integrate

    Connection to existing systems, testing with real data, training for the people who will work with it later.

  6. 06 Output

    Operate

    Monitoring, maintenance and further development – or an orderly handover to your team.

Prototyping

Measure first, then build

A prototype is not a preliminary version of the solution but a measuring instrument: it answers the one question the project hangs on – before a budget hangs on it.

  1. 01

    Functional prototype

    A rig that shows the critical function – no enclosure yet, but real measurements.

  2. 02

    Test rig

    Reproducible measurement series instead of gut feeling: you see limits, tolerances and margins.

  3. 03

    Basis for a decision

    Documented results, a cost envelope and a clear recommendation: carry on, build it differently or drop it.

Workbench

What we work with

Tools are a means, not an end. We choose them by asking who is meant to maintain the system in five years.

Application

  • PHP / Laravel
  • TypeScript
  • Vue
  • Blade
  • Tailwind CSS

Embedded

  • C / C++
  • Rust
  • MicroPython
  • ESP32
  • STM32
  • Raspberry Pi

Data

  • PostgreSQL
  • MySQL
  • SQLite
  • Redis
  • Time series

Protocols

  • MQTT
  • Modbus
  • OPC UA
  • CAN
  • REST
  • WebSocket

Operations

  • Linux
  • Docker
  • CI/CD
  • Monitoring
  • Backups

Hardware

  • KiCad
  • Oscilloscope
  • Logic analyser
  • 3D printing
  • Soldering

Frequently asked questions

Frequently asked questions

From what size does custom development pay off?

It is less the size that decides than the deviation. If a process is essential to your business and no standard product covers it without detours, in-house development often pays off with just a handful of workstations. If, on the other hand, there is an established product that hits 90 per cent, we will say so – and would rather help with the integration.

Do you handle hardware too, or only software?

Both. We design circuits, lay out printed circuit boards and build functional prototypes – and we write the firmware and the application to go with them. For series production, approvals and certification we work together with partners and support the handover.

How do we start if there is no specification yet?

That is exactly the normal case. We begin with a conversation about the problem and write a short technical assessment from it. If an assumption is unclear, we settle it in a small stage of its own – only after that do effort and schedule take shape.

Who owns the source code and the documents?

You do. Source code, schematics, layout data and documentation pass into your ownership together with the project. We work with widely used tools and open formats so that you are not dependent on us.

Can you take over an existing project?

Yes. Usually we begin with a review: what exists, what is sound, where does the risk lie? From that comes a recommendation – continue, repair selectively or replace. This assessment is usable even without a follow-up assignment.

Where do you work, and how does the collaboration run?

We are based in Grenchen and work in Switzerland, Germany and Austria – mostly remote, and on site for measurements, commissioning and workshop work. Communication in German, English, French, Italian or Spanish.

Describe the problem, not the solution.

A short outline is enough: what happens today, what should happen and where it gets stuck. We reply with an initial technical assessment – free of charge and without a sales pitch.