Integration and portfolio solution
The playground is the last ring binder nobody has digitised.
Playground equipment needs looking after all year, and EN 1176-7 sets out how: three levels of inspection, and a record of what was done. Almost nobody has that in a system. If you already have the units – as an integration partner, a group or a managing agent – this is a module you can add, not another product somebody has to choose to buy.
Three ways to use Lekko. Many need more than one.
For integration partners
Playground inspection as a module in your system
Already have the system that boards and managing agents sign in to? We connect Lekko to it with an API, event notices and an embedded view in your colours.
- Property management software and owner portals
- Facilities and maintenance systems
For your own brand
Lekko under your own name
Want to offer playground inspection to your own customers without building anything? Run Lekko as it is, with your logo and your colours. No developers.
- Managing agents and housing companies with their own customers
- Anyone who would rather offer it in their own name than build it
For groups and chains
One overview of every unit
Fifty nurseries or three hundred housing associations? Then the problem is knowing which units are not doing the inspection. A group structure and a portfolio ranked by risk.
- Kindergarten and school groups
- Municipalities and districts
- Property managers and housing companies
For integration partners
The user should not have to sign in somewhere else.
If you already have the portal that boards and managing agents use, that is where the playground belongs. The inspection can sit as a view in your app, in your colours, with the sign-in the user already has – or you can take the data over the API and build the interface yourself.
Your brand, not ours
Logo, colours and typography are set per partner. No Lekko branding if you do not want it.
One status field, if that is enough
If all you want is “playground: critical defect” on the property card, that is one API call.
Mobile first, because the round is outdoors
The inspection itself is done with a phone on the playground. The embedded view is built for that.
Birchwood Owners' Association · Health & safety
Playground
7 items of equipment · Last checked 24 July
An embedded view – your colours, your sign-in, your navigation.
API and events
Everything the app does can be done over the API.
Read to show the status where your users already are. Write to create units automatically as they are created with you. And get a notice when something needs doing, so you do not have to ask us every fifteen minutes.
Status for your own dashboard
{
"data": [
{
"id": "unit_8fk21",
"name": "Birchwood Owners' Association",
"external_id": "OBJ-40182",
"status": "critical",
"equipment_count": 7,
"open_defects": { "minor": 2, "moderate": 1, "critical": 1 },
"oldest_open_defect_days": 34,
"inspections": {
"routine_visual": { "last": "2026-07-24", "next_due": "2026-07-31" },
"operational": { "last": "2026-06-02", "next_due": "2026-08-16" },
"annual_main": { "last": "2025-09-11", "next_due": "2026-09-11" }
},
"report_url": "https://api.lekko.tech/v1/units/unit_8fk21/report.pdf"
}
],
"next_cursor": "eyJvIjoyNX0"
}Create a unit the moment it is created with you
{
"name": "Northbay Housing Cooperative",
"external_id": "OBJ-40199",
"organization_id": "org_kunde_4471",
"template_id": "tpl_housing_cooperative_standard",
"users": [
{ "email": "board@northbay.eu", "role": "admin" },
{ "email": "caretaker@facilityservice.eu", "role": "inspector" }
]
}
→ 201 Created
{ "id": "unit_91xz4", "status": "ok", "setup_url": "https://app.lekko.tech/…" }A notice when something needs doing
{
"event": "defect.critical",
"created_at": "2026-07-30T09:14:22Z",
"unit": { "id": "unit_8fk21", "external_id": "OBJ-40182" },
"defect": {
"id": "def_2p07m",
"equipment": "Swing by the sandpit",
"finding": "Worn S-hook in the suspension",
"severity": "critical",
"action": "The equipment is closed off",
"due_date": "2026-07-31"
},
"signature": "sha256=a91f…"
}A REST API over the whole data model
Everything the app does can be done over the API: units, equipment, inspections, defects and reports. Read to show the status in your own interface, write to create units and equipment automatically.
- Organisations and units – create a unit the moment a housing association is created with you
- Equipment with type, position, photo and history
- Inspections with the result per checklist item, and who carried it out
- Defects with severity, due date, assignee and closing date
- The report as PDF or structured JSON, for a chosen period
Notices when something happens
You should not have to ask us every fifteen minutes whether anything has changed. We tell you the moment it happens, so the event lands in your own notification system, your task list or your own tracking of deadlines.
- defect.created and defect.critical – a critical finding can open a case with you automatically
- inspection.completed – update the status in your portal in the same second
- inspection.overdue – the chasing can go through your own channels, in your own tone
- Signed messages, and new attempts if a call fails, so no event is lost if your system is down for a while
An embedded view in your colours
To the user it should look like part of your portal. The inspection flow can sit as a view in your app, with your logo, colours and typography.
- The inspection, the defect list and the report as embedded views
- Your own colours, logo and name – no Lekko branding if you do not want it
- Works on the phone, which is where the inspection actually happens
- Or the other way round: just one status field per unit, which you show in your own interface
The sign-in the user already has
Nobody should have to remember a password for something they use four times a year. Users come in with the account they already have with you.
- OIDC or SAML against your identity provider
- Or a signed handover from your backend – the user notices no sign-in at all
- Roles are steered on your side and mirrored on ours
- Remove a user with you, and the access is gone with us
New units set themselves up
An integration that needs manual work per unit does not scale. New units are created automatically from your system, with the right settings from day one.
- Create the unit, the users and the roles in one call
- Standard checklists and intervals come from a template you control
- When a unit ends with you, it is archived with us – with the history intact
A test environment before anything is live
You get your own sandbox with test data, your own keys and no connection to real units. Your developers can finish building before anybody takes a decision.
- Separate API keys for test and production
- Realistic test data: units, equipment, inspections, defects
- Notices sent to your test environment
For your own brand
The same app. Your logo and your colours.
Not everyone wants to build an integration, and nobody should have to in order to offer playground inspection to their own customers. Run Lekko as it is, with your profile over it. We set it up – you need no developers.
Organisation
Birchwood Owners' Association
Status
Equipment
Inspections
Defects and actions
Status
Birchwood Owners' Association
3 things need your attention
The list below shows what to do.
To follow up
Overdue inspection
Swing
Visual inspection overdue
Defect · Moderate
Worn S-hook
Swing
Organisation
Birchwood Owners' Association
Status
Equipment
Inspections
Defects and actions
Status
Birchwood Owners' Association
3 things need your attention
The list below shows what to do.
To follow up
Overdue inspection
Swing
Visual inspection overdue
Defect · Moderate
Worn S-hook
Swing
Your profile, not ours
Your logo and colours right through the app. Your customers recognise who it comes from, both in the interface and on the report they file away.
- We set up the logo and the colour profile
- The report comes with your logo in the header
The same product, no separate version
This is not a copy that falls behind. It is the same app everybody else uses, with a different profile over it.
- New features arrive at the same time as for everybody else
- Fixes and security updates come along automatically
- No separate codebase to maintain – for either of us
You own the customer relationship
The customers are yours. We run the service and keep the checklists current, and stay in the background.
- A separate organisation per customer, gathered in your overview
- You see the portfolio across them all, the customer sees only their own
- What your terms say about Lekko is agreed when we set it up
Up and running without developers
The whole difference from the platform route: here there is nothing to build. We set up the profile, you invite the customers.
- We set up the profile and the templates
- You add the customers, or we import a list
- Your first customer can be running without anybody writing code
Margins, who carries support and who invoices the end customer are agreed per partner. If you take the support and the billing yourself, the agreement looks different from when we do. Get in touch and we will go through it properly.
For groups and chains
The problem is not one inspection. It is knowing who is not doing them.
With fifty nurseries or three hundred housing associations, the question is never “how do we carry out an inspection”. It is “which of our units are in the worst shape right now”. That is what the portfolio dashboard answers – sorted by risk, not by the alphabet.
312
units
6
critical defects
23
overdue inspections
94 %
done in the last 30 days
| Unit | Region | Equipment | Status | |
|---|---|---|---|---|
| Birchwood Owners' Association | Amsterdam | 7 | Critical defect | Open for 34 days |
| Sunnyside Kindergarten | Warsaw | 12 | Overdue | Visual inspection 19 days over |
| Northbay Housing Cooperative | Vienna | 4 | Due soon | Operational inspection in 4 days |
| Linden Road Day-care | Lisbon | 9 | Open defects | 2 moderate, due 12 Aug |
| Harbourside Owners' Association | Dublin | 5 | In order | Main inspection 11 Sep |
| Hillside Kindergarten | Milan | 14 | In order | All levels up to date |
Showing 6 of 312 · Sorted by risk: critical defects, then overdue, then due soon
A group structure with shared requirements
Build the structure the way the organisation actually looks: group, region, unit. Settings are made once at the top and apply to every unit below, with room for local adjustments where they are needed.
- As many levels as the organisation has – group, region, municipality, department
- Checklists, intervals and reminder lead times apply downwards
- A unit can add items of its own, but cannot remove the group's
- Move a unit between regions without losing its history
A portfolio dashboard ranked by risk
Not a list of every unit in alphabetical order. A list that starts with the unit you should call today.
- Critical defects first, then overdue inspections, then what falls due soon
- Filter by region, kind of unit or the person responsible
- See how long a defect has been open – not only that it is open
- Units that have reported nothing at all are shown on their own
Delegated administration
A regional manager should see their own units, not all of them. Whoever looks after a single kindergarten should not be able to change the group's checklists.
- Roles per level: group, region, unit
- Read-only roles for the board, for health and safety, and for whoever reviews the documentation
- A change log: who changed what, and when
Shared checklists, steered centrally
If every unit is to check the same things, somebody has to be able to decide that in one place. Change the template and it applies from the next inspection across the whole portfolio.
- Add an item centrally – it appears for everyone on their next round
- Different templates for different kinds of unit: kindergarten, school, outdoor area
- The history shows which version of the template an inspection followed
A year plan and staffing across the units
A weekly round at fifty units is fifty rounds a week. The year plan shows what is due when, per unit and per person, so the work can be shared out before it falls due.
- The rounds due this week and this month for a whole region, on one screen
- Units without an active person responsible are pushed to the front – holidays and staff turnover are the commonest reason things stall
- The reminder goes to the person who is actually going to do the job, not to a shared inbox
Same equipment, same fault, several units
If the S-hook is worn on one swing model, it is probably worn on the other nineteen of the same model. The equipment is registered with its type and manufacturer, so a finding can be looked up across the whole portfolio.
- Find every unit with the same equipment type or the same manufacturer
- See whether a finding repeats – and where nobody has looked yet
- Numbers to take to the supplier, instead of a feeling
Outsiders get access only where they should
The annual main inspection is a job for a competent person. That person, the maintenance contractor and whoever reviews the documentation all need different access, and none of them needs to see the whole portfolio.
- Give a competent person access to selected units, for a limited period
- The maintenance contractor can record inspections without being able to change templates
- A read-only role for the board and for reviewers
- The access runs out by itself – no forgotten users
One report for the whole portfolio
One report for the group, one per region, one per unit – all from the same data. For the board, and for whoever reviews it.
- PDF to read, Excel and the API to work on further
- Choose the period and the level: last quarter for one region, last year for everything
- Key figures over time: the share of inspections carried out, and the average time from finding to closing
One agreement, one invoice
The units should not each order separately with their own card. A group agreement with a price per unit, and one invoice.
- A price per unit, agreed on volume
- One invoice to head office, with the units listed
- One data processing agreement for the whole group – not one per unit
Structure and shared requirements
Set the requirements once. Let them apply everywhere.
Build the structure the way the organisation actually looks, and set the checklists, intervals and reminder lead times at the top. They then apply to every unit below. A regional manager sees their own units – not all of them, and not only their own one.
- Group, region and unit – as many levels as you need
- Add a checklist item centrally, and it applies from the next round
- A unit can add local items, but cannot remove the group's
- A change log: who changed what, and when
Applies downwards from the group
- Checklists and items of your own
- Intervals and reminder lead times
- A requirement for a yearly main inspection
- Report template and logo
Several organisations
Many units does not always mean one organisation.
A group owns its units itself. A managing agent looks after units for customers who each own their own. A municipality has departments with the same requirements and different people on the ground. That decides who is the controller under the GDPR, who the documentation belongs to and what happens when an agreement ends – so the set-up is not the same each time.
The group
One organisation, many units
GroupRegionUnit
The group owns the units itself and answers for them. The requirements are set at the top and apply downwards, and the portfolio is one data set with one owner.
- One controller, one data processing agreement, one invoice
- Checklists and intervals are decided centrally
- Regional managers see their own units, head office sees them all
- Key figures can be compared between regions, because the basis is the same
The managing agent
Many customers, each with their own units
Managing agentCustomerUnit
A housing company or a managing agent looks after units it does not own. Each customer is their own organisation with their own data – you see every customer, the customer sees only their own.
- The customers are kept apart: nobody sees another's units, defects or photos
- You have a managing role across them all, with one work list for every customer
- The report goes out in the customer's name, with the customer's logo
- If a customer ends the management agreement, the data follows the customer – not you
The municipality
Several departments, the same requirements
MunicipalityDepartment or districtUnit
Schools, nurseries, parks and housing sit under different departments, each with its own people on the ground, but with the same requirements and the same political accountability. The minimum requirements are set centrally, the doing sits with the department.
- Shared minimum requirements for every department, set in one place
- Each department looks after its own units, with its own people and contractors
- One overall status for the chief executive and the elected representatives, without asking the departments to report by hand
- Everything can be pulled out as PDF or Excel – for the files, for access requests and for anyone who asks to see it
Customers you manage
37 organisations · 214 units
Each customer is their own organisation. The customer sees only theirs, you see them all – and the report goes out in the customer's name.
The customer sees theirs. You see them all. Nobody sees each other's.
For a managing agent, each customer is a separate organisation with its own documentation and its own data processing agreement. The line between them is not a filter in the interface, it is the structure itself – and that is why you can have one work list across them all without the customers sharing anything.
It also gives a simpler answer to the question nobody likes asking in a sales meeting: what happens if we stop working with you. The data belongs to the customer, not to the management agreement.
What applies whichever model you use
The units are kept apart until you say otherwise
The starting point is that an organisation sees only its own units. Access across them is something you give deliberately, to a role and a level – not something that follows from two units sitting in the same system.
A unit can have both an owner and a managing agent
The unit has one owner, and the owner owns the documentation. Other organisations can be given access to it – typically a managing agent, a maintenance contractor or a competent person. The role decides what they can do, and the report goes out in the owner's name.
If a unit changes owner or managing agent, the history stays with the unit
The unit moves to the new organisation with its equipment, inspections, defects and photos. The previous manager's access is removed. Nobody should have to start their documentation again because a contract was renegotiated.
The units come in without manual work
Three hundred units do not get typed in by hand. They can be read in from a spreadsheet with name, address, region and the person responsible, or created over the API from the system you already have. The equipment is registered on the first round on site, with a photo and a position.
Roles and access
Five roles, and what each of them can really do.
“Delegated administration” means nothing until somebody sees the table. Whoever looks after a single unit should be able to do the job without being able to change the group's requirements, and a competent person who comes in for one annual main inspection should not see the rest of the portfolio.
| Can | Group | Region | Unit | Inspector | Reader |
|---|---|---|---|---|---|
| See the portfolio overview | Yes | Own | Own | No | Own |
| Carry out an inspection | Yes | Yes | Yes | Yes | No |
| Record a defect | Yes | Yes | Yes | Yes | No |
| Close a defect | Yes | Yes | Yes | No | No |
| Add local checklist items | Yes | Yes | Yes | No | No |
| Change templates, intervals and due dates | Yes | Own | No | No | No |
| Invite users and set roles | Yes | Own | Own | No | No |
| Pull out a report | Yes | Own | Own | Own | Own |
| See the change log | Yes | Own | No | No | No |
“Own” means your own level and the units below it. The inspector is whoever walks the round – a caretaker, a maintenance contractor or a competent person – and does not need to see the rest of the portfolio. The reader is the board and anyone reviewing the documentation.
Security, privacy and operations
Everything a buyer needs to see is already out there.
The data processing agreement, the list of sub-processors, where the data sits and how it comes out again – published and versioned. You can start your assessment before you speak to us.
Little personal data to assess
Lekko is about equipment, dates and findings. The only personal data is the name and e-mail address of the people who sign in, so an inspection can be traced to a person.
Data inside the EU and the EEA
The database and the photos are with Amazon Web Services in Frankfurt (eu-central-1). E-mail goes through a supplier with servers in Ireland.
The data processing agreement and sub-processors are online
The data processing agreement and an up-to-date list of sub-processors are published and versioned. You do not have to ask for them before you start your assessment.
Everything can be taken out again
The whole data set can be exported as Excel, PDF and JSON – equipment, inspections, defects and photos. No lock-in, and we mean that seriously: the documentation belongs to the organisation, not to us.
Change log
Who did what, and when. Across a portfolio that means an inspection is not only recorded, but traceable to a person and a moment.
Built on the standards, not on our reading of them
The checklists follow the structure of EN 1176 and EN 1177, with a reference on every item. That makes each item something you can cross-check against a competent person's report, instead of having to take it on trust.
The data processing agreement and the privacy policy are published and versioned – you do not have to ask for them to start your assessment.
Why Lekko is easy to build on
A small subject, a small data model – and requirements that do not change every year.
One data model, not five integrations
Equipment, inspection, checklist item, defect, remedial action. The model is small enough to read in half an hour, and still covers everything EN 1176 and EN 1177 describe about inspection. It is the reason an API is possible here at all.
The content is part of the product
The checklists, the guides and the help pages are curated content with sources, not text somebody once wrote. That is the part that takes longest to build up, and the part that cannot be copied overnight.
The requirements change slowly
EN 1176 and EN 1177 are revised from time to time, but the basic requirements stay put. A product built on them is not made obsolete by the next shift in technology.
The market is everyone with a playground
Housing associations, cooperatives, nurseries, schools, municipalities, parks. Looking after a playground follows the ownership, and it is the same job whether somebody has three items of equipment or three hundred.
How we get started
Four steps, and none of them is big.
- 1
A half-hour conversation
You tell us what you have and who is going to use it. We say which way is the right one – API, embedded views, group structure, or a combination.
- 2
We sketch the solution in writing
Which endpoints and events you need, how the structure and the sign-in are set up, what is owned by whom. Short enough to read, concrete enough to decide on.
- 3
A pilot on a few units
Ten units, one region, or one customer. Enough to see whether it works in practice, small enough that nobody is taking a large risk.
- 4
Roll-out at your own pace
A group agreement, one invoice, and new units set up automatically from your system. We stay close through the first few weeks.
Questions and answers
Can Lekko sit inside our own system, without a separate sign-in?
Yes. The inspection flow, the defect list and the report can sit as embedded views in your portal, with your logo, colours and typography, and with sign-in from your identity provider. Or you can simply take the data over the API and build the interface yourself.
We manage units for several owners. Can the customers be kept apart?
Yes. Each customer is their own organisation with their own units, defects and photos, and no customer sees another's. You get a managing role across them all, with one work list for the whole portfolio. The report goes out in the customer's name, and if a customer ends the management agreement, the data follows the customer.
Can one unit sit under two organisations?
The unit has one owner, and the owner owns the documentation. Other organisations can be given access to it – typically a managing agent, a maintenance contractor or a competent person doing the annual main inspection. The role decides what they can do, and access can be given for a limited period.
What happens if a unit changes owner or managing agent?
The unit moves to the new organisation with its equipment, inspections, defects and photos, and the previous manager's access is removed. The history stays with the unit. Nobody should have to start their documentation again because a contract was renegotiated.
How do we get three hundred units into the system?
The units are read in from a spreadsheet – name, address, region and the person responsible – or created over the API from the system you already have. The equipment is registered on the first round on site, with a photo and a position. A portfolio usually goes live region by region, not all in one day.
Can we steer the checklists centrally?
Yes. Templates are set at group or region level and apply to the units below. A unit can add items of its own where there are local conditions, but cannot remove the group's. The history shows which version of the template an inspection followed.
Who owns the data?
The organisation that recorded it. The whole data set can be exported as Excel, PDF and JSON, photos included. We think that is a point rather than a formality: your inspection records should not be something you lose by changing supplier.
What personal data does Lekko process?
The name and e-mail address of the people who sign in, so an inspection can be traced to a person. The rest is equipment, dates and findings. That makes the privacy assessment short.
Where is the data stored?
Inside the EU and the EEA. The database and the photos are with Amazon Web Services in Frankfurt (eu-central-1), and e-mail goes through a supplier with servers in Ireland. The data processing agreement and a versioned list of sub-processors are published on the website.
What does this ask of us technically?
For a plain API integration: that your system can make HTTP calls and receive notices. For sign-in without a password: an OIDC or SAML set-up, or a backend that can sign a handover. You get a test environment with your own keys before anything touches real units.
How is a group agreement priced?
A price per unit, set on volume, with one invoice to head office and the units listed. For an integration we also agree how the set-up work is paid for. We set the price in conversation – it depends too much on the number of units and on what the integration has to do for a list price here to be any use.
What is the first step?
A half-hour conversation, where you tell us what you have and who is going to use it. Write to us through the contact form and choose “Integration or partnership”, and we will take it from there.
You have the units, we have the rest.
Tell us what you have and who is going to use it. We will say which way is the right one, and what it asks of you.