Frequently asked questions
The questions we get asked most often, grouped by topic. Can't find your question here? Feel free to get in touch.
General
CodeSprinter works for organisations with a research-driven or social mission. That could be research organisations, knowledge institutions, foundations, social organisations or commercial companies, for example. The legal form matters less to us than the goal the software is being built for.
No. It's enough if you can explain the problem you want to solve or what you want to achieve. In our first conversations we map out together which solution fits and what features you'll need for it.
No. We work for both for-profit and non-profit organisations. What matters most is that research or social impact is a real part of the project or the organisation.
Yes. You don't need a technical plan, a design or a complete list of features yet. In fact, at an early stage we can help you think through what's needed and which approach makes sense.
Software development
Custom software is especially worth considering when existing solutions don't fit your processes, users or goals well enough. That might be the case when you need specific functionality, want to connect several systems, or want to support a process that no off-the-shelf solution covers properly.
No. We can also develop individual components, build integrations or extend existing software, depending on the technical situation and the problem at hand.
That depends on the technology used, the quality of the existing code and the available documentation. We first look at how the software is built and whether developing it further makes sense technically and practically.
In many cases, yes. If another system offers a suitable API or another technical way to connect, we can look into how both systems can talk to each other.
That varies from project to project. The timeline depends on things like the size, complexity, number of features and any external dependencies. Before development starts, we map out the scope so it's clear what will be built and what planning fits with it.
There's no fixed price, because every project is different. After the intro and the project plan, we prepare a quote based on the agreed features and scope. If your budget calls for it, we can look together at which parts take priority and where things can be adjusted.
We set out ownership arrangements clearly up front. The starting point is that you don't become unnecessarily dependent on CodeSprinter and that it's clear which software and data belong to your organisation.
AI-driven software
Yes. AI models can misinterpret information, draw incorrect conclusions or convincingly give an answer that isn't true. That's why, with AI-driven software, we don't just look at how the model works, but also at the consequences when the model makes a mistake. Depending on the application, we can build in human oversight, validation steps or restrictions, for example.
That depends on the role AI plays within the software. In some applications, AI can carry out a simple task independently. In others, it's important that a user reviews, adjusts or approves results first. From a Human-Centered AI perspective, we look deliberately at that division between people and technology.
That depends, among other things, on which data is processed and which AI technology is used. We look, for example, at which information a model actually needs, where data is processed and which external parties may be involved in the processing. For sensitive data, additional technical and organisational measures may be needed.
Not necessarily. Some AI solutions use models from external vendors, while other models can run within a more protected environment. Which approach is appropriate depends on the project, the desired functionality, the sensitivity of the data and any requirements from your organisation.
Not necessarily. When it's relevant for a project, we can design the software so that the AI layer doesn't become unnecessarily entangled with one specific vendor. That can make it easier to switch to a different model or vendor later. Full interchangeability isn't always possible, however, because models have different capabilities and interfaces.
AI software requires a different way of testing than traditional software. Alongside technical tests, we look at realistic situations, the quality of the outcomes, edge cases and situations where the model makes mistakes or is uncertain. For applications where people work together with the AI, it also matters whether the outcomes are understandable and usable in practice.
Not every problem needs AI. If the same goal can be achieved reliably with traditional software, that can be simpler, more predictable and cheaper. That's why we first determine what you want to achieve, and only then investigate whether AI genuinely adds value.
Technology
That depends on the project. We work with Python, Django, React and TypeScript, among others, but we don't choose technology just because we're familiar with it. We first look at what the software needs and then determine which technical approach fits.
Because different applications have different requirements. A simple internal application has different needs than software that processes large amounts of data, contains complex integrations or is used on different devices. A fixed technical blueprint could therefore create unnecessary limitations.
That depends on the type of data and how the application works with it. For many projects we use relational databases such as PostgreSQL. In other situations a different solution may fit better. In making that choice we look at reliability, structure, performance and maintainability, among other things.
In many cases, yes. If another system offers a suitable API or other technical interface, we can investigate how information can be exchanged between the two systems. We also look at security, reliability and the dependence on the external party.
No. Container technology can offer many advantages for consistent deployments and management, but not every application needs the same infrastructure. We only use Kubernetes when the scale or complexity of the environment calls for it.
Where appropriate, we automate the process by which software is tested and deployed. This helps bring changes to a test or production environment in a controlled way and reduces the chance of manual errors. The exact setup depends on the project and the hosting environment.
When it fits the application and the management arrangements, we set up monitoring and logging. Monitoring provides insight into the technical health and performance of a system. Logging helps investigate errors and unexpected behaviour.
We try to build software in a clear and maintainable way. That means, among other things, paying attention to structure, technical dependencies and preventing unnecessary complexity. No technical choice makes software future-proof without limits, but a good foundation makes future changes considerably easier.
That's the starting point. We try to build software so that it can be understood by more than just the original developer. How easy a handover is naturally also depends on the size of the project, documentation and the technologies used.
How we work
We start with an intro conversation. In it we discuss your organisation, the problem, the goals and your first ideas. After that we work towards a project plan that makes clear what needs to be built.
Yes. We like to work in steps and regularly show what we've built. As soon as it's possible, we make a staging environment available where you can test features yourself and give feedback.
Yes, but changes can affect the planning, scope and budget. So we always discuss first what a change means and whether it fits within the existing arrangements.
Then we look at the priorities together. Using the prioritisation we made earlier, we can decide which features are essential and which could be postponed, adjusted or left out.
Managed hosting
Managed hosting means CodeSprinter doesn't just provide the technical environment, but also actively manages it. That can include infrastructure, monitoring, backups, certificates and technical updates.
No. Managed hosting is a separate service and is offered separately from development.
No. You can decide for yourself how you arrange hosting. If you'd like CodeSprinter to manage the technical environment, we can offer a managed hosting solution for it.
Managed hosting is about the infrastructure the application runs in. Managed software maintenance is about the application itself. You can combine both services.
Yes, when this is part of the hosting arrangements. The exact frequency, retention periods and recovery options depend on the application, the data and the requirements of the project.
That depends on the chosen hosting environment and the requirements of the project. If there are specific requirements around data location, privacy or security, we take them into account when setting up the environment.
We maintain the technical components of the hosting environment and assess relevant security updates. Which updates are needed and when they're applied depends on the infrastructure used and the impact on the environment.
We use monitoring to make technical problems in the hosting environment visible. When an incident occurs, we investigate the cause and determine what action is needed. Response times and availability depend on the service arrangements that apply to the environment.
Not by default. The level of availability and incident response depends on the arrangements made for the environment. If 24/7 availability or specific response times are needed, that has to be explicitly agreed in advance.
An Autonomous System Number, or ASN, is used to independently manage network traffic on the internet. Because CodeSprinter manages its own IP space and its own ASN, we have more control over certain network components and are less dependent on one specific hosting provider. For clients, what matters most is that this gives us more technical flexibility and control.
Where appropriate, we can use container technology and Kubernetes to manage applications and infrastructure. Not every application needs such an environment. We choose the infrastructure based on what the project requires.
Yes. If usage, capacity or technical requirements change, we can investigate which adjustments to the environment are needed. The exact possibilities depend on the architecture and hosting setup.
Managed software maintenance
Managed software maintenance focuses on the technical upkeep of your application after it has been delivered. Think of technical updates, investigating problems and work needed to keep the existing software well maintained.
No. Managed hosting is about the technical environment the application runs in, such as infrastructure, network, monitoring and backups. Managed software maintenance is about the application itself. You can combine both services.
No. Software development and managed software maintenance are separate services. After delivery, you can choose to have CodeSprinter stay involved in the technical upkeep of the application.
No. New features and larger functional changes fall under further development. If you have new wishes, we discuss what's needed and make separate arrangements for that.
That depends on the cause and the arrangements that apply to the project. A technical problem that arises while using the software can fall within maintenance. Problems caused by, for example, a new external integration or a desired functional change may require separate work. We make clear in advance which work falls under the maintenance arrangements.
Yes, when this is part of the maintenance arrangements. We assess relevant updates and also look at possible consequences for the existing application. Not every new version has to be installed right away. What matters most is that the software stays technically healthy and manageable.
Sometimes. We first look at the technical state of the application, the technologies used and the available documentation. Based on that, we determine whether we can responsibly take over the maintenance.
We investigate the cause and determine which solution is needed. How incidents are handled and which response times apply depends on the maintenance arrangements that have been made.
Yes. Maintenance ensures the technical continuity of the existing software. Alongside that, we can take on new wishes and features as separate further development.
Privacy and security
Yes. Privacy and security are built into the design and development of the software from the start. Which measures are needed depends on the type of data, the users and the context of the project.
The GDPR isn't a general technical checklist that automatically makes a software supplier or application compliant. We develop with care for privacy and data protection and help translate relevant requirements into technology. The ultimate legal responsibilities depend on the organisation, the data processing and the division of roles within the project.
Yes, as long as it's clear what requirements come with it. During the project we discuss which technical and organisational measures are relevant for the type of data being processed.
We look at the purpose of the application and try to process only the data that's actually needed for it. Which data is or isn't needed is determined together with the client.
That depends on the users and roles within the application. We can work with different permissions and access levels, so users only get access to information and functionality that's relevant to them.
Where appropriate, we use encrypted connections and technical measures to protect data in transit and at rest. Which measures are needed depends on the sensitivity of the data and the hosting environment.
That depends on the chosen hosting environment and the requirements of the project. If there are specific requirements around data location, privacy or security, we take them into account in the technical setup.
Retention periods are determined by the purpose of the processing, the arrangements within the project and any laws or regulations. CodeSprinter can help support these choices technically, but the substantive and legal responsibility lies with the organisation processing the data.
We build software so that technical maintenance and updates remain possible later. When CodeSprinter takes care of software maintenance or hosting, relevant security updates can be part of that service.
With AI applications we look at, among other things, which data is processed with models, where that processing takes place and which external parties may be involved. Human control and the consequences of incorrect AI outcomes can also be part of the design.
We can help with the technical information needed to make privacy risks and data flows transparent. For legal advice or formal privacy assessments, additional expertise is usually needed.
No. No software system can guarantee absolute security. The goal is to limit risks with appropriate technical and organisational measures and to design software so that it can stay well maintained and secured.
Working together and getting in touch
No. You don't need to know which programming language, database or infrastructure is required. We explain technical choices in plain language and advise on the approach.
Yes. We keep the lines short, so questions, choices and feedback can be discussed directly.
Yes. After delivery you can opt for managed hosting, managed software maintenance and any further development.
Get in touch and tell us briefly what you're working on or what you want to achieve. You don't need a fully worked-out plan yet. We'll discuss the problem first and then look together at which next step makes sense.
Can't find your question here?
Feel free to get in touch and tell us briefly what you're working on. We're happy to think along with you.
