Freelance Laravel backend development
Scope
What I build
Data model and domain rules
A PostgreSQL schema and rules the application applies itself. In the CRM I build at ONEXO.pl, that means protection periods counted in business days, commissions held in reserve and monthly statements locked once published.
REST APIs
An API for a frontend, a mobile app or device automation. I choose authentication per client: where credentials can be stored, how access expires and how it can be revoked.
Queues and background work
Redis queues with Laravel Horizon, so you can see which jobs are running and which failed. When a job touches several systems, I plan what gets retried and what gets undone.
Integrations
Connections to external services, with one system owning each piece of data, so they don’t end up holding different versions of it.
Admin panels
FilamentPHP for the admin side, so you don’t pay for a separate internal panel built from scratch.
Access and audit
Login and permissions, limits on exposed endpoints and, where records may have to serve as evidence, an audit log that detects edits.
Process
How it starts
- You email me what the application does or should do, where the code lives, if there is any yet, and what you need first.
- I read the code or the requirements and reply with the scope and what I would do first.
- I work in your repository and on your accounts, so the code stays with you from the first commit.
- We go through the code and the documentation together, so your team can carry on without me.
Background
Where this comes from
I have worked commercially with PHP and Laravel since July 2022, from a Laravel 5.8 event platform in my first job to a Laravel 13 CRM at ONEXO.pl. The details are in my work history.
My largest freelance project was a device provisioning platform in Laravel 11 with PostgreSQL and Redis queues. It handled batches of hundreds of devices in a test environment and never ran in production. On zeskanuj.com I was responsible for the architecture, backend and data model in a two-person team; development stopped before a beta when the funding ended.
Two notes show how I approach specific problems: A tamper-evident audit log in Laravel and Session authentication for web, tokens for mobile.
FAQ
Common questions
Can you take over an existing application?
Yes. I start by reading what is there: the code, how it is deployed and what isn’t written down anywhere. Then I propose what to change first, keeping the parts that work. At ONEXO.pl I took over another developer’s order app for Altholz, moved it to the client’s own server and fixed the key findings of its security review.
Do you also work on the frontend?
Backend is my main work. For admin screens I use Filament, and at ONEXO.pl I also build client websites in Next.js and React.
How much time can you give a project?
I work alongside my job at ONEXO.pl, usually on one specific problem or a defined piece of work, and I take a limited number of projects at a time.
Do you also handle deployment?
Yes, if you need it. That work has its own page.
What do I have at the end?
Code and documentation in your repository and on your accounts, so your team can continue without me.
To discuss a Laravel project, email maciej@jasiewicz.pro or see the contact page.