Your order

Website Hosting

VDS

Domain registrations

Total due 0 ₽
Make your website easy to find — register a domain today. Register a domain
Remember me
Sign in with VK
We will send a confirmation link to your email. After confirmation, you will create your password yourself.
Partner code
Sign up with VK

Website improvement For Laravel projects

Laravel website improvement and support

We fix errors, add features and develop existing Laravel projects: websites, stores, customer accounts and internal services. We also take on projects built by other developers. You can start with one task: first we get to know the project and agree on the scope of work.

Tasks

What is happening to the project and what we do about it

Six situations owners of Laravel projects come to us with. Each one shows what is usually behind it and where we start.

After an update or a change the site started throwing errors

After an update of PHP on the hosting, a package or a piece of code, some pages answer with an error or behave differently. The cause is almost always written in the error log: it only has to be read and reproduced.

What we do

  • we find the cause in the log and reproduce the error
  • we fix it and check the neighbouring scenarios the change touched
  • if a package is to blame, we pick a compatible version or a replacement
  • laravel.log
  • composer
  • PHP 8

A form, a payment or an exchange with a service works only sometimes

A request is sent, but the manager does not see it. The customer paid, but the order stayed unpaid. Usually one link of the chain breaks: a notification from the payment system, an email, a service API that changed.

What we do

  • we walk the chain from the customer’s action to the recipient and find the break
  • we fix the handling of notifications, repeated and failed requests
  • we add a log record so that the next failure is visible at once
  • webhook
  • API
  • mail

The customer account or the admin panel lacks a feature

Managers need a status, a report or an export; customers need documents and order history. The project does not have to be rewritten for that: a new feature is built into the existing data, permissions and interface.

What we do

  • we work out how the data and roles are organised now
  • we add a section, a field, a status, a report or an export
  • we take permissions into account: who sees what and who may change it
  • Eloquent
  • policies
  • Filament

An import, a mailing or a scheduled task does not run

The price list should update at night, emails should go out after an order, invoices should be issued at the start of the month. In Laravel the queue and the scheduler are responsible for that. When a queue worker stops or cron does not fire, the site looks alive while the work is not being done.

What we do

  • we check whether the queue workers and the scheduler are running on the server
  • we go through the failed jobs: what exactly did not run and why
  • we set up retries, time limits and a failure notification
  • queue
  • schedule
  • cron
  • supervisor

Pages open slowly

The catalog, the order list or a report take longer and longer to load, and it gets worse as the data grows. Most often the page makes hundreds of unnecessary database queries or recalculates every time what could be calculated once.

What we do

  • we measure where the time goes: queries, code, external services
  • we remove unnecessary queries, add indexes and a cache where it fits
  • we move heavy operations into background jobs
  • N+1
  • indexes
  • cache

The project runs an old version of Laravel or PHP

The hosting drops an old PHP version, a package you need requires a recent Laravel, and upgrading is scary: nobody knows what will break. This is solved by an assessment before the work starts, not by upgrading blindly.

What we do

  • we look at the versions, the dependencies and the packages that are no longer maintained
  • we lay out the upgrade path step by step: what passes untouched and what has to be replaced
  • we upgrade on a copy and check the key scenarios before switching
  • composer.json
  • Laravel
  • PHP
Discuss a task Your task is not on the list? Describe it as it is, and we will say whether we take it on

A Laravel store and a task about the catalog or orders? Online store improvement

The site is not on Laravel? Website improvement and modernization

Someone else’s code

Was the project built by another developer? We take it on

We start from the task and from getting to know how the project works today. It does not have to be rewritten for that: we look at the code, the deployment and the environment, and then suggest the nearest step.

About access. Passwords, the .env file and keys are not needed in the request. Which access the task requires and how to hand it over is something we discuss after the first conversation.

What we look at first

  • the Laravel and PHP versions, the set of packages
  • how the project is deployed to the server and whether there is a copy for testing
  • the error log, the queues and the scheduled tasks
  • which services are connected: payments, mail, external APIs
  • whether there are tests and documentation, and how to work if there are none

What you get after the review

A short description: what we saw, how your task is solved and what it costs. If the Laravel version or the packages limit the solution, we say so right there, before the work starts.

Experience

We work with Laravel every day

All five projects in our portfolio run on Laravel, and each of them can be opened. Two of them in more detail: a customer’s store we keep developing after launch, and our own website.

Customer project

KratonShop: an equipment store

In January 2026 the store moved from an old system to Laravel, and the work went on, driven by the owner’s tasks and buyers’ feedback.

  • Yandex rejected the product feed. We analysed the format and changed how the feed is built. The repeat check on 6 January 2026 showed 8,384 offers, all without errors.
  • The delivery calculation from an external service loads when the buyer opens the delivery tab and does not delay the product description.
  • Search understands the Russian spelling of Latin brand names: the query "хансман" finds Hansmann.

Detailed case study Project in the portfolio Open the site

Our own project

Siteko.net: the site you are on

Hosting, domains and VDS. Storefront, cart, payment, customer account and admin panel live in one Laravel project we develop ourselves. What people bring to us is what we deal with at home every day.

  • payment acceptance, invoices and fiscal receipts
  • integrations with domain registrars and the hosting panel
  • queues and scheduled tasks: service renewals, reminders, emails
  • the upgrade from Laravel 12 to Laravel 13 was done on our own project

Project in the portfolio Open the site

Three more Laravel projects

  • InterTooler

    The store catalog is filled by imports from supplier files and feeds, and prices in foreign currency are converted at the exchange rate.

    Project in the portfolio
  • TransElCon

    A bilingual company website with a Filament admin panel, moved from Joomla 1.5 with the page addresses kept.

    Project in the portfolio
  • Iris Piter

    A wholesale store with a buyer account and catalog export to Excel, moved from MODX Evolution.

    Project in the portfolio

The whole portfolio

How it works

From one task to ongoing support

  1. You describe the task

    What is happening and what should come out of it. The project address and, if you know them, the Laravel and PHP versions and what the problem started after.

  2. We get to know the project

    We look at as much as this task needs: the code, the error log, the way it is deployed. We ask for access separately and only for what is needed.

  3. We agree on scope, cost and verification

    We write down what is included, what it costs and how you will make sure the task is solved. Work starts after you agree.

  4. We do it and check it

    We make the change and check the agreed scenario and the ones next to it. The order of deployment to the live site is settled in advance.

  5. We discuss what is next

    The next task follows the same order. That is how a one-off fix becomes ongoing support at the pace the project needs.

Cost

What the estimate depends on

A task that sounds the same, say "fix the payment", takes different time in two projects: in one the cause is visible in the log right away, in the other a copy of the project has to be set up first and a home-made module studied. So we name the amount after getting to know the project and agree on it before the work starts.

You can start with one task. A large one is split into stages: you know the amount for each before it starts.

Discussing the task and a preliminary estimate do not commit you to anything. A detailed code audit is separate work: if it is needed, we say so in advance and agree on its scope.

Discuss a task
  • the task itself and the result you need
  • the state of the code: versions, packages, tests, documentation
  • the integrations the change touches
  • whether there is a copy of the project for testing or it has to be set up first
  • how the change is deployed to the live site

Questions

Frequently asked questions

Will you take on a project built by another developer?

Yes. We start from your task and from getting to know the current implementation: we look at how the project is built and deployed, then suggest the nearest step. The project does not have to be rewritten for that.

Can I come with a single error?

Yes. A single error is a separate task with its own scope and estimate. A large project or a support contract is not required to get in touch.

What about an old Laravel version?

First we look. Often the task can be solved on the current version and the upgrade planned separately. If the version or the packages get in the way, we say so after the check and suggest an upgrade path step by step.

Do I have to move the project to your hosting?

No. Working on the project is not tied to buying hosting: it stays where it is. Whether the current environment suits the task is something we see along the way: for example, whether the PHP version is enough and whether queues and scheduled tasks can run.

How do you estimate the work without a ready spec?

It is enough to describe what is happening and what should come out of it. We ask the questions ourselves and write down the scope of work before the estimate. That becomes the spec.

What access will you need?

None in the request: do not send passwords, the .env file or keys. After the first conversation we agree which access the task needs (to the code, the server or the admin panel) and how to hand it over.

What does the timing depend on?

On the task and the state of the project. We name the timing after the review, for the agreed scope of work. If the site is down right now, say so in the request: it affects where to start.

Did not find an answer? Ask your own question

Laravel project

Tell us about the project, and we will discuss the task and an estimate

Describe what is happening and what should come out of it. You can attach a screenshot of the error.

Laravel project improvement request

Only the task description and one way to reach you are required.

What to write: the project address, what is happening and what should come out of it, the Laravel and PHP versions, if you know them.

One way to reach you is enough. If you leave both, we will also reply by email when a call does not go through.

By sending the request you agree to the personal data processing policy.

What happens next

We reply to the contact you leave: we ask questions and tell you how we see the scope of work.