Skip to content

Frankfurt am Main

soft

BSoftware development

Tools for processes that exist only at your place.

Off-the-shelf software covers eighty per cent. The remaining twenty cost your team hours every week. That is exactly where we start, with small applications instead of large projects.

An aisle between two rows of server racks whose status lights glow blue

We begin with the case, not with the technology: who does what, where the process breaks, which data sits where. After that comes a working slice through the entire application, before anything is built out.

That way you see early whether the direction is right and can steer the scope while doing so is still cheap. Whatever is finished goes into service, even if the rest is still missing.


B.1Fields

Four fields we build in.

Interfaces
Two systems that know nothing about each other, and a person copying data between them: that is the most common job that reaches us. We build the connection, including error handling and a log, so that it can be traced later on what actually happened.
Automation
Producing reports, collecting files, reconciling stock, watching deadlines. Whatever runs the same way every week afterwards runs by itself at night and only speaks up when something is wrong.
Business applications
When there is no suitable off-the-shelf software for your process: a lean application with a database, user permissions and reporting. Start small, grow it on real cases.
Operation
We operate what we build: in containers, with backups, monitoring and a tested way back. On request we hand over to your own IT instead, with documentation and a handover meeting.
A screen in a dark room on which a wireframe layout builds itself box by box

( Merksatz )

A working path first, the build-out second.

A narrow path through the whole application shows more after two weeks than a slide deck does after two months. It also shows what is still missing.

B.2Tools

What we work with.

Languages
TypeScript and Python for most things, SQL for everything that involves data.
Data
PostgreSQL and MariaDB, plus file storage with clear permissions instead of network drives that grew over the years.
Operations
Docker on our own servers, a reverse proxy with automatic certificates, backups with restore tests.
Handover
Source code, documentation and credentials are yours from day one.

None of this is an end in itself. We pick what fits the problem and what another team can carry on with later.

B.3From our own house

What comes out of it, we use ourselves.

digoCockpit is management software for condominium and rental property that we built and run ourselves. One shared body of data instead of many lists, master data that knows which period it belongs to, entries that are not altered after the fact, and statements whose arithmetic is there on the page.

It stands here because it is the same kind of build we do for clients. The only difference is that with this one we are developer and user at once, and notice every fault first.

digocockpit.de

B.4Enquiry

A process that is costing you time?

Describe it in a few sentences. After one conversation it is usually possible to estimate whether automating it pays off, and from when.

Describe your case