Customer portal
We maintain customer portals with sign-in and data, matching application and database care to traffic, data and critical functions.
Your app in expert hands.
Managed hosting for applications.We look after the environment and the technical operation of your application.We diagnose problems in its code too.
Explore the care scopeWhat can we take care of?
We tailor care to how your application works and what your business needs.
Business system
A system handles users, tasks and data exchange across tools. We match care to dependencies and response needs.
Online service
An online service with several connected parts for multiple customers. We match care to its architecture, workload and continuity needs.
Choose your care.
From a stable portal to an application that daily operations depend on.We match care to its functions, dependencies and importance to your business.
Standard
For a stable application that needs ongoing oversight, technical maintenance and occasional fixes.
Ongoing care
Subscription quoted after an application review
- Hosting and technical maintenance
- Application monitoring and diagnosis
- An agreed allowance for minor fixes
Business
For an important application: priority support, regular checks of key processes and changes with a test environment.
Support priority
Subscription with agreed support availability
- Priority incident handling
- Oversight of key processes
- A regular work allowance and test environment
Bespoke
For a complex application that needs its own architecture, suitable resources and tailored support arrangements.
Project and care
Setup and maintenance defined in the project
- Architecture and resources suited to your needs
- Dependencies and integrations in one plan
- Agreed continuity terms
Pricing depends on the environment, application dependencies, code work and required support availability. The offer separates application onboarding, resources and licences, ongoing care and an agreed work allowance.
Your environment and code under our care.
We combine managed hosting with technical application maintenance.When a problem arises, we look for its cause in the code too.
Environment and dependencies
A stable foundation for your application.
We select and maintain the environment, database and accepted dependencies. We oversee resources, certificates and services needed to keep it running.
Diagnosis and code fixes
One technical owner for the problem.
We diagnose environment and application code issues. Agreed fixes use the work allowance; larger repairs and development are quoted before work begins.
Updates and protection
Changes are checked before release.
We maintain security and agreed updates for the application and its environment. We test changes with a rollback plan, then check the application after deployment.
Monitoring and recovery
Backups and recovery are part of your care.
We monitor services and agreed application functions. We back up data and plan application recovery based on how important the system is to your business.
Compare what is included.
Compare environment maintenance, code work and the level of cooperation.We agree the details after reviewing the specific application.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Use case | A stable portal or dashboard | An application for daily operations | A complex application and its dependencies |
| Maintenance | The environment and accepted application | The environment and key processes | Scope based on the architecture |
| Code work | Fixes from the agreed allowance | A regular application work allowance | Budget and scope defined in the project |
| Support level | Standard working hours | Priority and an agreed response | Availability suited to business needs |
Environment and resources
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Application and database | The accepted application and its database | Application and key dependencies | Services and roles defined in the project |
| CPU and memory | Resources suited to the application | Resources suited to peak workloads | Resources based on the architecture |
| Data and files | Capacity for data and its growth | Capacity suited to business processes | Data and expansion plan |
| Background tasks | Accepted tasks and schedules | Oversight of important task processing | Dependencies defined in the project |
| Test environment | Scope suited to the change process | An environment for deployment checks | Environments and the delivery process |
Application diagnosis and maintenance
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Problem diagnosis | Included, with code analysis | Included, with priority | Based on accepted dependencies |
| Code bug fixes | From the available work allowance | From the regular work allowance | From the agreed budget |
| An error after our change | Verification and service recovery | Verification and service recovery | Acceptance under the change process |
| External provider | Diagnosis and agreed escalation | Priority diagnosis and coordination | Responsibilities defined in the project |
Diagnosis and agreed recovery actions are included in the subscription. Permanent fixes to third-party code use the accepted allowance. If recovery requires a code fix after the allowance has run out, we agree further work and its price before starting; diagnosis and available recovery actions continue within ongoing care. We fix our own errors without using the client's hours.
Updates and safe deployments
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Operating system and runtime | Maintenance of the accepted configuration | Maintenance of the accepted configuration | Based on the architecture |
| Code libraries and dependencies | Scope agreed after review | Update and compatibility plan | A plan for the whole system |
| Tests after a change | Checks of agreed functions | Checks of key business processes | Deployment acceptance scenarios |
| Deployment rollback | A plan suited to the type of change | A plan for the application and its data | A procedure based on dependencies |
| Major version change | Assessment and a separate scope quote | Assessment and a separate scope quote | A separate modernisation stage |
Routine security and functional updates compatible with the accepted environment are included in care. A migration requiring a rebuild or repair of unsupported dependencies is quoted after assessment; a new version number alone does not trigger an additional charge.
Monitoring and backups
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Automated monitoring | Availability, services and resources | Services and important application processes | Coverage based on the architecture |
| Functional checks | An agreed operating scenario | Agreed critical processes | Scenarios for dependent services |
| Data backups | Schedule and retention set out in the offer | A profile suited to the rate of data changes | Data protection plan |
| Recovery support | Within the accepted care scope | Support priority | Under the continuity plan |
| Recovery objectives | Requirements agreed before onboarding | We select a recovery profile | Design and verification of objectives |
We agree the monitored functions, resources, backup schedule and recovery objectives. Automated monitoring runs around the clock.
Contact and response time
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Office hours | Mon–Fri 09:00–17:00 (Warsaw) | Mon–Fri 09:00–17:00 (Warsaw) | Work windows and availability in the offer |
| Incident handling | Under the agreed support arrangements | With priority and an agreed response time | Support level defined in the project |
| Outside office hours | Subject to availability and agreement | Priority, with terms set out in the offer | Separately agreed availability |
| Repair time | Depends on the cause and scope | Depends on the cause and scope | Objectives set out in the recovery plan |
Operator working hours and the time to start handling an incident are defined in the cooperation terms.
Changes and billing arrangements
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Application work allowance | Scope and period set out in the offer | A regular allowance agreed in the offer | Budget based on the engagement |
| Programming work | Fixes and work on the code | Fixes and work on the code | As agreed for the engagement |
| Administration work | Environment and database configuration | Environment and database configuration | Based on the architecture |
| Additional administration | PLN 300 net / h by agreement | PLN 300 net / h by agreement | Based on the accepted quote |
| Additional programming | Rate confirmed in the offer | Rate confirmed in the offer | Based on the project and technology |
| New features | Separate quote and acceptance | Separate quote and acceptance | A separate project scope |
The offer defines the allowance, its validity period and how administration and programming are billed. We specify a shared or separate budget for these activities and additional-work rates; we do not convert hours without agreement.
Ongoing maintenance, monitoring, compatible updates and incident handling within the accepted scope are included in the subscription. They do not use the planned-change allowance. Fixing an error caused by our change does not use the client's hours either.
The accepted application, database and machine are covered by one care scope. An additional subscription applies to new responsibilities or a separate environment.
Pricing depends on resources, services and integrations, code care, backups and required support availability. Before purchase, we separate onboarding, the subscription, licences and additional work.
Technologies
| Technology | Standard | Business | Bespoke |
|---|---|---|---|
| PHP / Laravel | Code and startup assessment | Code and business process assessment | Architecture and dependency assessment |
| JavaScript / TypeScript | Code and startup assessment | Code and business process assessment | Architecture and dependency assessment |
| Python | Code and startup assessment | Code and business process assessment | Architecture and dependency assessment |
| C# / .NET | Code and startup assessment | Code and business process assessment | Architecture and dependency assessment |
Before we begin
Before onboarding, we review the code, environment and dependencies.
We document existing faults and quote the necessary repairs.
Ongoing care starts after repair or the client's informed acceptance of the documented limits.
Subscription and data handover
Monthly subscriptions with an onboarding fee have a one-month notice period.
The option without an onboarding fee has a three-month notice period.
We agree the scope of onboarding before the service begins.
Annual plans are paid for one year in advance.
Renewal terms and the settlement of early termination are set out in the agreement before the service starts.
When the service ends, we hand over the files, database, code you own, configuration and start-up instructions.
One plan covers the accepted environment and its components; we do not charge for the same database or machine again under a second subscription.
From review to ongoing care.
- 01
Understanding your application
We review the code, functions and environment dependencies. We identify issues and the work needed to take over the application safely.
- 02
Agreeing the terms
We agree scope, support availability, allowances and billing. The offer separates onboarding, subscription, licences and extra work.
- 03
Taking over care
We organise access, monitoring and the deployment process. We check the application and rollback plan before ongoing care begins.
Questions about application care.
Can you take over an application from another developer?
Yes, after reviewing the code and environment. We document existing issues and agree what needs fixing before ongoing care begins.
Do you analyse the application code too?
Yes. We also use AI agents to review code and prepare fixes. We verify changes through tests and checks of the running application.
Are bug fixes included in the subscription?
Diagnosis and agreed recovery actions are included in the subscription. Permanent fixes to third-party code use the agreed allowance; once it runs out, we confirm further scope and pricing before work begins. Fixing our own error does not use your hours.
What about an application built with AI assistance?
The same principles apply as with any other code. We check whether it can run, its security, dependencies and condition, then define the onboarding terms.
How do you handle integration issues?
We diagnose accepted connections and coordinate resolution within the agreed scope. Availability and changes to external services also depend on their providers.