Cleaner cities. More efficient operations. A better tomorrow.
NexaWaste PRO + NexaWorks is a single platform for waste management, fleet management and field work - for cities, municipal companies and field teams.
Every collection is under control. Every service documented.
Select a stage to see who is responsible for it and what screen supports it.
STEP 1 OF 7
Order
An order is created from a contract, schedule, reservation or resident's notification. It has an address, waste stream or job type, and a deadline.
Screen for this stage: Collection calendar. Click on the screen to see the next one.
TWO PRODUCTS, ONE ENGINE
Waste and municipal services in one workflow.
NexaWaste PRO
NexaWaste PRO connects contracts, addresses, waste streams, bins, schedules, vehicles and collections in one workflow. Each collection has a plan, an assignee, evidence and a manager’s decision. Data flows into reports and billing without copying it between spreadsheets.
NexaWorks organizes greenery, cleaning, winter maintenance, roads and lighting works. Each task goes through the same workflow: order, assignment, execution, proof, manager control and billing. The module uses the same accounts and data as NexaWaste PRO.
RoadsWinter maintenanceGrounds maintenanceLightingCleaningPublic infrastructureTeamsInventoryInspections and reportsSubcontractors and settlements
PostgreSQL with forced RLS separates organization data. The application account does not have permission to bypass this policy.
Admin MFA
Administrator logs in with password and TOTP code. Passwords are stored as scrypt hashes.
Secure sessions
Session tokens are 256 bits long; only their SHA-256 hashes are stored in the database. Write operations require a valid Origin header and CSRF token.
Idempotence and versions
The operation key protects against double writes, and the record version against overwriting someone else's change.
Hash chain audit
The history is appended and linked with hashes. The app account cannot change or delete it.
Payment key vault
Stripe, Przelewy24 and Fakturownia keys are AES-256-GCM encrypted on the server. They don't go to the browser or APK.
INTEGRATIONS
Integration status, clearly explained.
Each adapter has a clear status: available, awaiting your credentials, or requiring implementation and acceptance testing.
LifeNexa CORE
SSO, licenses and subscription settlement. The development adapter is running in the pilot; production connection requires an agreed contract.
Requires a provider
Stripe
Hosted Checkout and signature verification notifications. The administrator enters the keys and performs a connection test.
To be configured in the panel
Przelewy24
Transaction registration, CRC check and verification confirmation. Requires an organization operator account.
To be configured in the panel
Fakturownia
Issuing invoices, PDF and payment synchronization. Requires an API token and an issuer department in your organization's account.
To be configured in the panel
BDO
Draft records and validation are available. Submission requires the organisation's credentials and API compliance acceptance, including after the 2027 changes.
Requires a provider
KSeF
Requires separate workflow, authorizations and tests. Not connected yet.
Requires a provider
GPS and telematics
An adapter for the provider selected by the organization. Actual positions appear after that provider is connected.
Requires a provider
RFID, QR and NFC
Identifiers are in the register. Hardware readers require an adapter and on-device testing.
Requires a provider
Scales
The weight is entered manually and marked as such. Certified scale requires an adapter.
Requires a provider
Email, SMS and push notifications
In-app notifications are available. Notifications outside the app require a configured provider.
Requires a provider
Maps (MapLibre/OSM)
Operational map with OpenStreetMap data and attribution. Lists also work without a map.
It works
NexaCity OS
Planned exchange via API and events, without copying the municipality's database. Not connected yet.
Requires a provider
A GOOD START OF COOPERATION
Know exactly what you are deploying.
The scope, data and acceptance criteria are determined before the pilot starts.
This is a platform for waste management and municipal works in the field. It combines the dispatcher's panel, applications for drivers and employees, and the resident portal. It is part of LifeNexa Enterprise.
Is the system ready for production?
Before starting work, the organization configures LifeNexa Enterprise access and completes acceptance of security and its own data.
Who is the platform for?
For waste collection companies, municipalities, municipal utilities, property managers and subcontractors. Each organization has isolated data and its own roles.
Does the system plan routes automatically?
The system suggests a collection sequence using vehicle capacity and time windows. Distances are straight-line estimates and do not include road traffic. A dispatcher approves the plan.
Are there real vehicles on the map?
After connecting a GPS provider and accepting the integration. Until then, the map shows locations and planned routes.
Is there integration with BDO and KSeF?
Draft BDO record entry and validation are available. Submission to BDO and KSeF integration require the organisation's credentials and compliance acceptance testing.
LET'S START WITH YOUR NEEDS
A cleaner city. A more efficient team. Let’s talk.
Choose a product and a conversation topic. The request will receive a number and go to the service center; We will respond to the address provided.
Presentation of real screensScope tailored to processesClear stages and acceptance criteria