No incidents
PLN 600 net / month
40 h availability × PLN 15 = PLN 600.
No additional work.
For developers and IT specialists · B2B
Get paid for being available.
With a team behind you.
Additional income for on-call availability, with incident work paid separately. You learn the system, follow prepared procedures and receive support from a service owner. Together, we work to keep incidents to a minimum.
Agreed availability windows. The required start time depends on the project.
Part of a team, supported by a service owner.
Preparation, escalation and cover organised for you.
Complementary skillsHow cooperation works
You and the teamshared responsibility
Service ownerknows the project
Preparationbefore you start
Escalationexpert support
Paymentavailability + work
Coverorganised for you
Proceduresclear actions
The service owner organises cover. Preparation for on-call work is paid.
One-month examplePLN 600 net for availability
40 h × example PLN 15/h. No incidents.
With two hours of workPLN 800 net in total
PLN 600 availability + 2 h × example PLN 100/h.
Clear cooperation termsAvailability + work
Rates and workload are illustrations, not an offer or a guarantee of assignments.
See billing examples ↗Example compensation · one month
Availability is paid.
Actual work is paid on top.
Each example assumes 40 on-call hours at PLN 15/h for availability and PLN 100/h for active work. These figures illustrate the model; they are not guaranteed rates or assignments.
With 2 hours of work
PLN 800 net / month
PLN 600 for availability
+ 2 h × PLN 100 = PLN 200.
With 5 hours of work
PLN 1,100 net / month
PLN 600 for availability
+ 5 h × PLN 100 = PLN 500.
B2B net amounts, before tax and costs. Work hours are billable hours after each incident is rounded up to a started 30-minute block. They are not a forecast of incident volume.
Project preparation is paid at the agreed hourly rate and is not included above. Availability is paid for every on-call hour, including during an incident. Active incident work is added separately. Each started 30 minutes is billable: 20 minutes is 0.5 billable hours; 35 minutes is 1 hour.
Cooperation example — not a promise of ticket volume
Five eight-hour windows.
40 hours of availability per month.
This is the volume used in the examples. Days and times are agreed per project. Availability is not eight hours of continuous work, but it requires a real ability to respond.
You learn and practise
After qualification, you learn the project, access and scenarios. Learning the system and practising procedures are paid at your agreed hourly rate. The required time to begin work after an alert depends on the project: up to 30 minutes in some cases and up to 4 hours in others. You know this, the escalation path and compensation before accepting a window. This is a time to start action, not a repair deadline.
You can begin an intervention
You receive alerts and must be able to use the agreed access from your computer and network. Whether other activities are possible depends on the response requirement. We do not assume every on-call window can be combined with your main job.
You act within known boundaries
You assess the situation, follow an approved scenario or escalate, and record time and findings. If an incident continues beyond the window, you continue handling it; it is not automatically handed over. After the window, only active work in started 30-minute blocks is paid and availability pay ends. Escalation still applies; you do not have to solve every issue alone.
Key cooperation terms
- Time to begin work
- Depending on the project: within 30 minutes or 4 hours of an alert. You know the requirement before accepting a window.
- Preparation
- Learning the system and practising procedures are paid at the agreed hourly rate.
- Incident billing
- Availability pay for the full window plus active work for every started 30 minutes. After the window you continue the incident, with active work only.
- Cover and payment
- The service owner organises cover. Monthly invoice with 14-day payment terms.
Why should there be fewer interventions over time?
Because of a proprietary method built through 10 years of system maintenance: project preparation, prevention and continuously improved procedures. This is a way of working, not a guarantee of quiet on-call windows. The compensation examples do not predict incident volume.
Different skills, one process
Where can your experience
help the most?
You do not need to cover everything. We match responsibility to your skills and the specific project.
You bring order to the situation
You receive a report, assess impact, gather context and perform approved basic actions.
You find the cause
You analyse logs and dependencies, work within granted access and procedures, and escalate when needed.
You solve harder problems
You contribute application or infrastructure expertise and help improve response scenarios and prevention.
From profile to potential cooperation
Fit first.
Responsibility follows.
We are building a network for future project needs. Applying is not a job offer or a guarantee of on-call work.
We learn about your experience
We discuss skills, availability and expectations, and assess what scope makes sense for both sides.
We practise scenarios
For a matching project, you learn the system, access, operating rules and escalation path before your first window.
We agree cooperation
We agree on-call windows and separate rates for availability and active work. Operational lessons return to the documentation.
A place for your skills
How would you like to work with us?
Tell us about your experience and availability. You will see a profile summary that will form the basis of a conversation.
B2B cooperation. Applying does not guarantee a project or any number of on-call windows.
Good to know before applying.
Is this employment?
Initially, we cooperate exclusively on a B2B basis. We are building a specialist network for potential future projects.
How does compensation work?
Availability and actual work are agreed separately. You state your expectations, which we assess against project scope and availability. We do not promise a number of hours or monthly earnings.
Will on-call windows be quiet?
Maintenance and prevention aim to reduce interventions. You must still be ready to respond within the agreed time; we do not guarantee incident-free windows.
Have a system that needs maintenance?
See how we work with businesses.