Run waste operations with one connected platform

Waste Pilot (ArcaneWaste) connects company fleets, customer rentals, driver jobs, Finix payments, and role-scoped chat—with realtime Pusher updates and FCM alerts.

4
Actor types · Company, Customer, Driver, Admin
V1
Unified API · /api/v1 REST + JWT
2
Chat types · order_company & job_driver
Finix
Payments · Merchant + customer charges

The problem

Dumpster rental operators juggle spreadsheets, phone calls, and disconnected tools for fleet status, driver schedules, order billing, and customer payments. Waste Pilot centralizes the operational truth in one API-backed system.

Waste management companies

Configure catalog, fleet, pricing, approve orders, dispatch drivers, collect payments.

Renters / customers

Browse specs, place orders, pay upfront or balances, request date changes.

Drivers

Check in, run nested job trees, submit evidence, report issues, share location.

Platform admins

Onboard companies, oversee customers, drivers, assets, and orders.

Everything connected in one API

Fleet, orders, dispatch, payments, and field operations—built from the actual Waste Pilot codebase.

Order lifecycle

Pending → approval → payment → dispatch → delivery → pickup → completion with status history and line-item billing.

Fleet & catalog

Assets, trucks, lots, stations, pricing profiles, taxes, promotions, and operational status tracking.

Dispatch board

Daily context API loads jobs, eligible drivers, trucks, assets, lots, and stations for routing decisions.

Finix + wallet

Card processing via Finix, optional wallet balance, company SaaS subscriptions, and transaction records.

Driver operations

Attendance, nested jobs, typed evidence, issues, and FCM.

Realtime chat

Company↔customer and driver↔customer threads with cursor pagination, unread counts, and Pusher events (new_message, messages_read).

From order to pickup

1
Place
2
Approve
3
Dispatch
4
Deliver
5
Pickup
6
Complete
Customer places order against an asset specification

Security & reliability

JWT authentication

tymon/jwt-auth with actor-type middleware on every protected route group.

Tenant isolation

company_id on tenant models; explicit scoping—no automatic global company scope.

Payment readiness gates

canAcceptPayments() and check.company.subscription on selected mutating routes.

Event-driven side effects

Notifications and wallet operations via EventServiceProvider listeners—not inline in controllers.

Built for real infrastructure

Finix

Card payments, merchant onboarding, SaaS billing

AWS S3

Media and document storage

Pusher

Broadcasting and chat channels

FCM

Push notifications to mobile clients

Ready to explore the system?

Read the developer docs, import Postman, or log in to open Telescope and application logs.

Home Features How It Works Architecture Documentation Postman Log in