Questions? No problem.

This can be done via Gitlab or by email. We review each report and classify it as a bug/incident, RFC or user question. Depending on the type and urgency, we apply corresponding response times.

No, an SLA is optional. However, an SLA does offer additional benefits such as guaranteed response times, a fixed point of contact and prioritisation of calls. Without an SLA, you can still use support.

Impact sessions are strategic sessions in which we look together at how your digital environment can be further optimised. We link insights to concrete tickets and build an ongoing roadmap together.

We work on a co-creation basis. This means that we work intensively with your team to come up with smart, scalable solutions together. We apply our C-U-B-E model: Create, Invent, Build and Evolve.

Our service package consists of a combination of maintenance, management, hosting, support (SLA) and development (strippenkaart). In this way, we ensure that your digital landscape remains secure, up-to-date and future-proof.

Sprint 0 is our inventory phase. In a few weeks, we completely map out the scope of a project: from goals and user requirements to technical requirements. In this way, we ensure a flying start and a solid foundation for what follows.

With the strip card you reserve a fixed number of hours per month for smaller RFCs (requests for change) and user questions. This gives you control over budget and capacity, and ensures that requests can be dealt with quickly.

With an additional SLA option, we offer out-of-hours reachability for high-prio incidents. This coverage runs from Monday to Sunday between 08:00 and 22:00. All hosting services are monitored 24/7.

Certainly, Cube is growing and our people are growing with us. So you can grow into a position with more responsibilities or a position with a different content. There are many different possibilities, depending on your knowledge and skills, hard- and softskills and your drive.

At Cube, the focus is on customer projects, but developing our own products is no stranger to us and is on the roadmap for the coming years. The scope of assignments varies. We have multi-year intensive collaborations with clients whose entire digital landscape we manage, and we work on projects with a clear head and tail. Every project is different, and every client has different requirements and starting points. Check the  cases on our website to get a good idea of this, At Cube, we focus on customization and innovation. That keeps our work varied. Do you have a preference for one or the other, or does a varied mix suit you well - just let us know! We try to take your personal wishes and preferences into account as much as possible.

You will work in the design team, but you will also collaborate a lot with external stakeholders to fully understand their needs and requirements. You will also work closely with colleagues from other departments, such as development and business, to create the right solutions and ensure the successful execution of projects.

The ideal size of a team is around nine people. Composition: two project managers and seven developers. When starting a new colleague, extensive consideration is given to knowledge, skills and the needs of the teams and the applicant to determine in which team the new colleague will do best. Each team has a Team Lead - this is one of the project managers - and a Tech Lead, this is one of the experienced developers. Each developer at Cube has their own specialism (e.g. front-end, back-end, app, Vue.js, Flutter, React Native or a combination thereof). In addition, several developers have Devops responsibilities.

Developing scalable, user-friendly applications and software solutions. You work together with project managers, UX/UI designers, developers, devops engineers and strategists to create the best solution for the client. Work efficiently, ask questions and learn from colleagues.

Your working day starts between 07.30 and 09.00. We have a joint break between 12.00 and 13.00. Your working day ends between 16.00 and 17.30. At Cube, we work 7.5 hours daily while you get paid for 8. This is in the second half-hour break (12.30 - 13.00). You get this extra time from Cube so you can take a break from work after lunch. Go for a walk with colleagues, play a game of football, darts or table tennis. If you want to go out on your own, no problem. Do what recharges you.

Cube employs both full-time and part-time employees. Depending on the role, we also have part-time options.

Learning on the job, our Hackathons, knowledge development hours, personal training and development programmes; all these contribute to the development of teams and individuals. Do you have a wish or an idea regarding development, training or workshop? Let us know. Then we will see what we can do. Basically, there is a training budget of EUR 750 per year for each team member.

Certification is possible! If you wish to obtain a professional certificate, we will be happy to help you. In recent times, for instance, colleagues have obtained certifications for Laravel, Vue.js and the implementation of the ISO 27001 standard.

Our office is in the heart of Oldenzaal, at the foot of the Plechelmus basilica and opposite the town hall. In front of the door is a large car park where you can park your car. If you come to meet us, we will switch on the parking meter for you. If you start working at Cube, we will arrange a parking permit for you. The current office has 45 fully equipped workstations. These are all equipped with a modern standing desk, ergonomic office chair and one or two 28" monitors.

Scalability is essential, because you want your API to grow with your business/product. We use techniques like load balancing, where traffic is distributed across multiple servers, and caching with tools like Redis, to make frequently requested data available quickly.

Security comes first. We implement the latest security measures, such as OAuth 2.0 for authentication, API keys for access management and SSL/TLS encryption for secure communication.

We provide customised integrations with all your external systems, such as your ERP, CRM, payment systems and marketing tools. This way, your systems exchange data with each other efficiently and securely.

The cost of creating a web application depends on the complexity, features and integrations required. At Cube, we start by identifying your needs and goals so that we can provide a solution that fits within your budget. Whether it's a simple tool or a complex platform, we ensure price transparency and an efficient development process.

Application development is the process of designing, building and maintaining software applications for mobile, web or desktop. This includes everything from UX design and architecture to programming, testing, deployment and support.

At Cube, we specialise in customised applications using modern technologies such as Flutter,  React Native,Vue.js, Livewire, Laravel. Whether it's a mobile app, web platform or fully integrated system, we deliver secure, scalable solutions that align with your business goals.

With MCP, the integration layer runs on your own infrastructure. You control which data is visible per tool and who has access. MCP supports authentication via OAuth or API keys, rate limiting, and logging. Data does not leave your environment unless you explicitly allow it.

A DMP ensures data is centralised and structured. MCP is the layer that gives AI models access to that data. They complement each other.

Yes, when implemented correctly. MCP runs on your own infrastructure. Cube always implements with permission management, authentication, and audit logging in line with ISO 27001.

The investment depends on the number of systems, the complexity of your data landscape, and whether a central data layer is needed first. A first MCP server for one system is typically operational within two to four weeks. Contact us for a tailored estimate.

An API is static and pre-programmed for a specific data flow. MCP is dynamic: the AI model discovers which tools are available and decides when to use them. In most organisations, both work alongside each other.

MCP focuses on server-side integrations with internal systems. WebMCP is a proposed browser standard from Google and Microsoft that allows websites to declare their capabilities as tools for AI agents.

MCP is an open standard that enables AI models to communicate in a controlled way with external systems such as CRM, ERP, or internal databases. Originally developed by Anthropic, it is now governed by the Linux Foundation.

Claude (Anthropic), models from OpenAI, Google, and Microsoft all support the protocol. A well-built MCP server works with any model that implements the standard.

Any system with an API can be connected, and some systems already have their own MCP server. Think CRM systems like HubSpot or Salesforce, ERP packages, planning tools, customer portals, and ticketing tools. What the MCP server can do depends on what that system's API allows.

Anthropic (the company behind Claude) introduced MCP in November 2024. In December 2025, governance was transferred to the Agentic AI Foundation under the Linux Foundation.

Most modern ERP integrations operate via an API. In more complex environments, a middleware layer is used to manage, translate, and monitor data traffic between multiple systems simultaneously.

In the Netherlands, these include AFAS, Exact, Microsoft Dynamics 365, SAP S/4HANA, and Unit4. The best choice depends on your industry, the size of your organization, and the complexity of your processes.

ERP stands for Enterprise Resource Planning: software that centralizes core processes within an organization, such as finance, procurement, inventory management, and HR. Well-known systems in the Netherlands include AFAS, Exact, Microsoft Dynamics 365, SAP S/4HANA, and Unit4.

The cost of an ERP integration varies depending on the situation. It depends on factors such as the number of systems that need to be connected, the quality of existing APIs, and the complexity of the business logic. Because no two integrations are the same, both the cost and the timeline can vary significantly. During an introductory meeting, an initial estimate can be made based on your specific situation and requirements. This quickly provides clarity on what is needed and what to expect.

An ERP integration is a technical connection between your ERP system, such as AFAS, Exact, SAP, or Microsoft Dynamics, and another application like an e-commerce platform, WMS, or CRM. Data is exchanged automatically, eliminating the need for manual input and making processes more efficient. The cost and implementation time of an ERP integration vary per situation. This depends on factors such as the complexity of your systems, the amount of data, and the desired functionalities. An initial estimate can be made during an introductory meeting, providing clarity on what is needed for a successful implementation.