TechinFlow services
TechinFlow offers fifteen services in three groups: building software, maps and geodata, and data and infrastructure. Eight services have an English page and are compared in the first table; the other seven are described in Dutch and listed in the second. Each row shows what the service is and who it is for.
Which services have an English page?
| Service | What it is | For whom | Typical technology |
|---|---|---|---|
| Custom software development | Software for a process that does not fit an off-the-shelf package | Organisations with their own work process or much manual work between systems | Python, TypeScript, PostgreSQL, REST APIs |
| Web and app development | Web applications, portals and mobile views | Teams that need an internal or public portal | React, Next.js, accessible HTML following WCAG |
| GIS and digital map solutions | Maps, geodata processing and geo-applications | Organisations with spatial data | OpenLayers, MapLibre, PostGIS, GeoServer, WMS/WFS, OGC API |
| GIS viewer for municipalities | A map viewer for staff and residents | Municipalities and joint arrangements | Open source viewer, PDOK services, RD and WGS84 |
| Open data platform | A portal where datasets are findable and reusable | Government bodies and organisations that publish data openly | CKAN or an alternative, DCAT metadata, open formats |
| Data platforms and data management | Bringing together, checking and exposing data from several sources | Organisations that report from scattered systems | PostgreSQL, Python pipelines, APIs |
| Cloud and data infrastructure | Hosting, backups, monitoring and maintenance | Organisations that want software and data to run reliably | Linux, containers, hosting in the EU |
| Technology and software consultancy | Advice on choices, architecture and tender requirements | Clients preparing a choice or a tender | Architecture sketch, requirements list, comparison on criteria |
The technology in the last column is an indication. What we use in an assignment depends on what already runs and what your organisation can maintain itself.
Which services are described in Dutch only?
Seven services are narrower variants of the ones above and have a page in Dutch only.
| Service | Group | What it is | For whom |
|---|---|---|---|
| App development (in Dutch) | Building software | Choosing and building a PWA, native or cross-platform app | Organisations that want an app for iOS, Android or the web |
| API integrations (in Dutch) | Building software | Integrations between systems and APIs of your own | Organisations that retype data or merge exports by hand |
| Legacy modernisation (in Dutch) | Building software | Replacing outdated software step by step | Owners of old custom, Access or Excel applications |
| GIS management and hosting (in Dutch) | Maps and geodata | Running map servers: updates, monitoring, backups | Organisations with their own GeoServer or PostGIS |
| From ArcGIS to open source (in Dutch) | Maps and geodata | Moving wholly or partly to open source GIS | Organisations that want lower licence costs or less dependence |
| Data warehouse for SMEs (in Dutch) | Data and infrastructure | One database for reports from accounting, web shop and CRM | Small businesses that paste reports together from exports |
| Dashboards (in Dutch) | Data and infrastructure | Dashboards on a documented database | Teams that want to track figures without manual work |
How the services fit together
The services form three layers that connect. At the top is the application people use: a portal, a form, a map viewer. Below it sits the data, whether that is geodata from national services, your own registers or datasets you want to publish. At the bottom is the infrastructure everything runs on, which someone has to maintain.
You can enter at any layer. A municipality that only wants a better map viewer starts with the GIS viewer for municipalities. An organisation that first wants to know which direction to take starts with technology and software consultancy. If you want to publish data, look at the open data platform and the guide on CKAN or an alternative (in Dutch). If you mainly want to use national data, the guide to Dutch open data lists the registers and their APIs.
The same principles apply to every service: open standards, open source where possible and exit requirements agreed up front, so that you receive source code, configuration and data in open formats if the collaboration ends. The page for each service describes what exactly is included, who it is not suitable for and which questions we ask beforehand.
Which service fits your question
If you are unsure which service fits your situation, start from the question you have now.
- You want to digitise a process that now runs on e-mail and spreadsheets. See custom software development or web and app development.
- You have records with an address or coordinate and want to see or analyse them on a map. See GIS and digital map solutions.
- You want to combine data from several systems for reports or a dashboard. See data platforms and data management.
- Your software runs on a server that nobody really understands any more. See cloud and data infrastructure.
If you work for a Dutch municipality, software for municipalities (in Dutch) sets out the frameworks that shape every choice. If none of this fits, describe your question through the contact page.
Related
More about TechinFlow
A new company in Haarlem building custom software, GIS and data platforms on open standards.
023 230 21 42Get in touchA question or project?
Tell us briefly what is going on and for which organisation. We reply by email.
Send a message