New Pro + Launch: pick a template and our developers set up your site in 2 business days.
See how it works
Build · Back-end & APIs

APIs, integrations and back ends that keep running

PHP, Laravel and Node.js – and the Joomla side of it: Web Services API, plugins on the event system, scheduled tasks. We design the data and the interfaces first, then build them with tests, logs and documentation.

Reviews on Trustpilot →
PHP 8.3Laravel Node.js Joomla Web Services API
Architecture

Joomla and a service, each doing its part

An example: Joomla keeps content and members; a Laravel service handles payments, syncs and the mobile app.

Joomla site Laravel service content · members · editors plg_system_sync · events Web Services API · tokens scheduled tasks · retries REST API · versioned queue jobs · idempotent webhooks · signed logs · monitoring · alerts Paymentscheckout · subscriptions CRMcontacts · members ERP / stockproducts · prices Mobile appsame API
Client systems

Back ends behind real products

Booking, portals, listings and search – built and maintained for clients.

Berth booking
Berth bookingMBCCS · booking for cruise agents
Agent portal
Agent portalMBCCS · schedules and bookings
Listing plans
Listing plansMF PropTech · recurring payments
Travel search
Travel searchVIVI CITY · Laravel back end
Which stack

The right place for the logic

Not everything belongs in Joomla – and not everything needs a separate app.

Inside Joomla

  • Components, plugins and scheduled tasks
  • When the data lives in Joomla and editors manage it
  • Web Services API for other systems

Laravel

  • Apps with their own data and users
  • Queues, heavy jobs, complex APIs
  • Talking to Joomla over its API

Node.js

  • Real-time features and websockets
  • Streaming and lots of open connections
  • Small services next to PHP
What we check

What every back end gets

The same checklist, whether it's a Joomla plugin or a Laravel app.

Architecture

Data, boundaries and who calls whom, written down before code.

  • data model
  • API contracts
  • sync direction

Database

Schemas that migrate cleanly and queries that stay fast.

  • migrations / sql updates
  • indexes
  • bound parameters

Security

The boring basics, every time.

  • CSRF + auth on every write
  • input filtering
  • secrets out of Git

Integrations

Third-party APIs that fail gracefully.

  • timeouts + retries
  • idempotent webhooks
  • rate limits

Performance

Measured under realistic load.

  • queues for heavy work
  • caching
  • profiling

Operations

Deploys, logs and backups you can rely on.

  • scripted deploys
  • structured logs
  • monitoring + alerts
For developers

Joomla as a good citizen in your stack

When Joomla has to tell another system about a change, we do it with a plugin on the event system – typed events, the core HTTP client, settings in the plugin, no core edits.

  • SubscriberInterface with typed events
  • Core HttpFactory with timeouts
  • Endpoint and token in plugin settings
  • Failures logged, never blocking the editor
final class Sync extends CMSPlugin implements SubscriberInterface
{
    public static function getSubscribedEvents(): array
    {
        return ['onContentAfterSave' => 'onContentAfterSave'];
    }

    public function onContentAfterSave(Model\AfterSaveEvent $event): void
    {
        if ($event->getContext() !== 'com_content.article') {
            return;
        }

        $item = $event->getItem();

        try {
            HttpFactory::getHttp()->post(
                $this->params->get('endpoint'),
                json_encode(['id' => (int) $item->id, 'title' => $item->title]),
                ['Content-Type' => 'application/json', 'Authorization' => 'Bearer ' . $this->params->get('token')],
                5
            );
        } catch (\RuntimeException $e) {
            Log::add('Sync failed: ' . $e->getMessage(), Log::WARNING, 'plg_system_sync');
        }
    }
}
A system plugin that sends saved articles to an external API.
How it runs

Six steps from spec to handover

Developers on your side can review every commit.

  1. Requirements

    Systems, data, volumes and what must never break.

    You getRequirements summary, fixed quote
  2. Architecture & API spec

    Data model, endpoints, events and error handling.

    You getAPI spec
  3. Build

    Code with tests, in your repository.

    You getCommits you can review
  4. Integrate

    Connected to the real third-party sandboxes.

    You getIntegration log
  5. Load & security test

    Realistic load, auth and input checks.

    You getTest report
  6. Deploy & hand over

    Deploy scripts, monitoring and documentation.

    You getDocs and runbook
Integrations

What we connect, and how

Every integration gets the same treatment: sandbox first, failures handled, logs you can read.

IntegrationTypical jobHow we build it
PaymentsCheckout, subscriptions, invoicesProvider SDK or API, signed webhooks, idempotent order updates.
CRMContacts, members, donationsSync in one direction per field, queued, with a conflict rule. See CiviCRM on Joomla 6.
ERP / stockProducts, prices, stock levelsBatched imports as scheduled tasks or queue jobs, with a dry-run mode.
SSO & social loginOne login across systemsOAuth / OpenID Connect through Joomla authentication plugins.
Your own APIMobile apps, partners, headless front-endsJoomla Web Services or a Laravel API, versioned and documented.
Real projects

Back ends we built

All projects
Who we work with

Agencies, in-house teams and site owners

Much of our work comes from other developers: agencies with client sites on Joomla, and teams who know their site but want senior Joomla hands for the hard part.

Agencies

We work under your name, in your repository and your ticket system.

  • White-label, NDA on request
  • One quote per site, or for a batch of client sites
  • Your client talks to you – we stay in the background

Developers

Hand us only the hard part and keep the rest.

  • One extension, one integration, or a review of your code
  • Commits and pull requests you approve

Site owners

One team for the whole job, explained without jargon.

  • A fixed quote before work starts
  • Maintenance after launch if you want it
What clients say

Clients on our back-end work

Vincenzo Galliano
Vincenzo GallianoCTO at Vivi City Network
“ThePixel led a full revamp of vivi.city … Their technical depth and reliable delivery made a real difference.”
Laravel · API · redesign
User-friendly but also incredibly fast
Volker AlsenOwner and CEO of Posada Nena
“They built a stunning website and an efficient travel booking platform for Posada Nena.”
Website + booking platform
Complete, well done and on time
Robert FarrisUS · on Trustpilot
“He has completed database work, configuration of modules, components and other items within the scope of work.”
Joomla development
A loyal client of thepixel for 3+ years
Abdullahi BusuriManaging Director, AdminPlans
“They consistently provide exceptional support and deliver outstanding results.”
Development · upgrades · servers
Outstanding UI and UX
John BarsonPublisher of Total Health Magazine
“The team is endlessly helpful, flexible and always quick to respond.”
Magazine site · UI/UX
FAQ

Back-end development questions

Not here? Ask in the forum or send us your project.

Can you work on an existing codebase?

Yes – most back-end jobs start there. We read it first, write down what we find, and change it in small, reviewable steps.

Can you upgrade our Laravel application?

Yes. We did it for VIVI CITY together with a redesign and a better product sync API. Upgrades go version by version with tests in between.

Do you write tests?

Yes, for business logic and integrations, run on every change. How far we go is part of the quote.

Where does the code live?

In your repository, with documentation and a runbook for deploys.

Should this be a Joomla extension or a separate app?

If the data lives in Joomla and editors manage it, usually an extension. If it has its own users, data and load, usually a separate app talking to Joomla over its API. We say which in the spec.

Get a quote

Describe the system. We reply in under 12 hours

“They built a stunning website and an efficient travel booking platform for Posada Nena.”
Volker Alsen · Website + booking platform
Reviews on Trustpilot →
  1. 01Tell us what has to talk to what, and the volumes involved.
  2. 02We write the spec: you get it with a fixed quote.
  3. 03You decide. Nothing starts before you agree to the plan.
Cron Job Starts