PHP developer in Prague

PHP development for Prague companies, done remotely by one developer in Poland: legacy PHP upgrades, Laravel, Symfony and WordPress back ends, with Czech personal data, e-mail marketing, accessibility and cybersecurity rules in view.

PHP developer

My place in the WordPress community

  • I have had a wordpress.org account since 2006.
  • I contributed to WordPress core for versions 7.0 and 7.1.
  • I maintain 30 plugins on wordpress.org.
  • I organise and speak at WordCamps.
  • I have attended every WordCamp Europe from 2017 to 2026.
  • Local WordPress meetup: NášWP WordPress komunita

My WordPress.org profile

If your company in Prague runs on PHP and the code needs an upgrade, a new back end or a second pair of hands, this page says what I do, what I do not, and how a project runs. I am Mariusz Szatkowski, one person, working with WordPress since 2006, and so writing PHP, from Gdynia in Poland. I am not a Prague agency, I have no office there, and I do not visit or take calls. All communication is written, in English.

I wrote it around the questions a technical owner in Prague has to answer anyway: which PHP version is still supported, what a legacy upgrade involves, and which Czech rules reach the code. Where the law is involved, I link the source and say which part is mine and which belongs to your lawyer.

#What the Prague market looks like for PHP work

The Czech Statistical Office puts the national ICT sector at 6.0% of business sector turnover in 2024, with 200,972 people employed (CZSO, ICT sector). Its Prague factsheet for 2024 gives the mid-year population as 1,387,354 against 10,886,531 for Czechia, and records 26 universities with 41 faculties and 124,706 students by place of study in 2024/2025 (CZSO, First hand figures Prague 2024). The same factsheet puts research and development spending in Prague at 2.7% of regional GDP in 2023, against 1.8% for Czechia.

Prague-Karlín, Czech Republic. Rohanské nábřeží, a footbridge.

Photo: ŠJů, CC BY 4.0, Wikimedia Commons.

I do not work for any institution named on this page and I have no client references from them. What the figures say to me is narrow. A city with that much research and that many students has plenty of PHP written by people who have since moved on, and plenty of applications that outlived their first author. That is the shape of brief I expect from Prague: an application that works, that nobody dares to touch, and a PHP version that is about to lose support. The first question I ask is which of the two you have, a system to keep alive or a system to start.

#PHP support dates on 11 November 2026

The table below is from php.net, supported versions, read on 11 November 2026. Each branch gets two years of active support and two more years of security fixes only.

PHPReleasedActive support untilSecurity fixes until
8.28 Dec 202231 Dec 202431 Dec 2026
8.323 Nov 202331 Dec 202531 Dec 2027
8.421 Nov 202431 Dec 202631 Dec 2028
8.520 Nov 202531 Dec 202731 Dec 2029

Two things follow. PHP 8.2 stops receiving security fixes at the end of this year, so an application still on it has weeks, not months. And anything older than 8.2 is not in the supported table at all.

The frameworks have their own calendars. The Laravel support table says bug fixes run for 18 months and security fixes for 2 years, and lists Laravel 12 with bug fixes until 13 August 2026 and security fixes until 24 February 2027 on PHP 8.2 to 8.5. Laravel 11 security fixes ended on 12 March 2026 (Laravel, release notes). Symfony lists 6.4 as a long-term release with bug fixes until November 2026 and security fixes until November 2027, and 7.4 as the current long-term release with bug fixes until November 2028 and security fixes until November 2029 (Symfony, releases). If your application is on Laravel 11 or Symfony 6.4, the upgrade plan is the first deliverable.

#Legacy PHP: how I approach an upgrade

An upgrade is not “change the version number”. I treat it as five written steps.

  1. Inventory. PHP version, framework version, Composer dependencies, extensions, cron jobs, and what the hosting offers. You send read access to the repository or an archive; I send back a list of what blocks the move.
  2. Tests around current behaviour. If there are none, I write characterisation tests for the paths that carry money or personal data before anything changes.
  3. Static analysis and automated refactors. PHPStan to find the removed functions and type problems, Rector for the mechanical changes between versions.
  4. Staging. The upgraded application runs on a copy with production-like data that has been anonymised, with outgoing mail switched off.
  5. Cutover plan. A written order of steps with a rollback path. I do not promise how many weeks this takes before I have read the code, because the honest answer depends on test coverage and on the dependencies that are no longer maintained.

For a WordPress site the same steps apply to the theme and plugins, and I test them against the target PHP version before I touch production.

CTU - New Building Dejvice, Prague, lecture halls

Photo: Czech Wikipedia user Utar, CC BY-SA 3.0, Wikimedia Commons.

#Laravel, Symfony and WordPress back ends

What I take on, in plain terms:

  • Laravel applications and APIs: business applications, admin panels, queues and scheduled jobs, REST endpoints with authentication and validation.
  • Symfony back ends: long-lived systems, integrations with ERP, CRM or accounting software, message queues, Doctrine data layers.
  • WordPress and WooCommerce plugins: custom plugins, REST routes, hooks, integrations with outside systems. I follow the WordPress coding and security standards instead of inventing my own.
  • Code quality: PSR-12 formatting, strict types, PHPStan in CI, tests on the risky paths, written notes for whoever maintains it next.

What I do not do: UI design, mockups or wireframes. Those come from you, and I implement them. I also do not take work I cannot support long term. If a request sits outside my range, I say so before the scope is signed.

For the WordPress side of a Prague project there are separate pages: WordPress developer in Prague and WooCommerce developer in Prague. If the front end is Astro or Next.js, see Astro developer in Prague and Next.js developer in Prague. The general service page is PHP developer.

#Czech rules that reach a PHP back end

I am not a lawyer and I do not give legal opinions. These are the acts a Czech company usually has in mind, with what each means for the code.

#Personal data: act no. 110/2019 Sb. and the ÚOOÚ

The Czech act on the processing of personal data is zákon č. 110/2019 Sb. alongside the GDPR (Regulation (EU) 2016/679). Under section 50 the Office for Personal Data Protection (ÚOOÚ) is the central administrative authority for the field, and its seat is Prague (ÚOOÚ). Three points matter for a back end:

  • Breach reporting. Under section 41, a controller reports a personal data breach to the Office without undue delay unless the risk to people is low. A report made later than 72 hours after discovery must include the reason for the delay. Section 42 adds notifying the affected people where the risk is high. A processor must tell the controller without undue delay (section 34).
  • Children. Section 7 sets the age at which a child can consent to personal data processing in relation to information society services at 15. If your application has accounts for minors, the sign-up flow has to account for that.
  • What I can do in code. Access control, audit logging of reads and exports of personal data, retention jobs that delete on schedule, and a documented list of where personal data sits. I cannot decide your legal basis for processing.

#E-mail marketing: act no. 480/2004 Sb.

Zákon č. 480/2004 Sb. covers some information society services. Section 7 allows commercial messages by electronic means only with the recipient’s prior consent. It allows an exception for a business’s own similar products sent to addresses obtained from a sale, provided the customer can refuse simply and free of charge, in every message. Messages that hide the sender or carry no valid address for refusing are prohibited.

For a Laravel or Symfony application that sends newsletters, this becomes concrete: store the consent with date and source, put a working unsubscribe link and address in every marketing message, and keep marketing and transactional mail on separate queues and templates.

#Accessibility: act no. 424/2023 Sb.

The Czech act transposing Directive (EU) 2019/882 is zákon č. 424/2023 Sb., effective from 28 June 2025. Section 2 lists e-commerce services among the consumer services it covers and excludes services provided by a microenterprise. The Czech Trade Inspection Authority (ČOI) supervises it, and its guidance defines a microenterprise as fewer than 10 staff with turnover or balance sheet total up to two million euros. The ČOI also says the act does not reach websites and mobile apps whose content has not changed since 28 June 2025, and that updated content must then comply (ČOI, accessibility for businesses).

If you run an online shop with a PHP back end, whether you are in scope is for you and the ČOI. What I add is the part in the code: keyboard-operable checkout, labelled fields, readable error messages, and an HTML output that a screen reader can follow.

#Cybersecurity: act no. 264/2025 Sb.

The new Czech cybersecurity act, zákon č. 264/2025 Sb., has been in effect since 1 November 2025 and implements the NIS2 Directive (Directive (EU) 2022/2555). It names the National Cyber and Information Security Agency (NÚKIB) as the central authority. Section 18 covers, among others, cloud computing, data centres and managed services providers. Whether your company or your customer is a regulated provider is decided by that act and NÚKIB, not by me. If you are a supplier to a regulated company, ask them what they expect from you, and send me the requirement in writing so that it lands in the scope.

#Seven checks for a PHP application in Prague

  1. Check which PHP version production runs. If it is 8.2, schedule the move before 31 December 2026.
  2. Check the framework version against its support table: Laravel 11 and Symfony 6.4 are the two to look at.
  3. Run composer audit and list the packages with no maintainer.
  4. Count the tests that cover payment, login and personal data export. If it is zero, that is your first job.
  5. Write down where personal data lives: database, logs, backups, mail tool, analytics.
  6. Name the person who reports a breach to the ÚOOÚ and how fast they can reach the logs.
  7. For marketing mail, find where the consent is stored and whether every message carries a working way to refuse.

#How a PHP project with me runs

  1. You write first. Repository or site URL, goal, deadline, current PHP and framework version.
  2. I read the code and answer with written questions and the risks I see.
  3. I write the scope, with assumptions and acceptance criteria. Work outside it is estimated separately, in writing, before I start.
  4. You provide repository access, a staging environment or permission to create one, and test data. If screens change, layout and graphic design come from you. I implement them.
  5. I build on staging, with outgoing mail off and payment gateways in test mode.
  6. You accept the work against the criteria in the scope.
  7. I hand over written notes: what changed, how to deploy, how to roll back. Ongoing maintenance is a separate, optional arrangement: WordPress maintenance in Prague for WordPress sites.

Replies come in writing on working days. Calls and meetings are not part of how I work, and I promise no response time.

If you are a software house in Prague and need an extra pair of hands on a defined slice, such as one module or one upgrade, the same written process applies. You stay the client-facing party and I work to your scope.

#Questions Prague companies ask

#Are you a Prague agency?

No. WPPoland is me, Mariusz Szatkowski, writing from Gdynia in Poland. Prague has no office of mine and no team stands behind this page.

#Which PHP version should a Prague company run today?

php.net lists 8.2 to 8.5 as supported on 11 November 2026. PHP 8.2 gets security fixes only until 31 December 2026, so target 8.4 or 8.5. Anything older than 8.2 is not in the supported table.

#Do you work on Laravel and Symfony or only on WordPress?

Both. Laravel and Symfony back ends, REST endpoints and integrations, and custom WordPress and WooCommerce plugins. If a job is outside what I can support, I say so in the scope.

#Who is the data protection authority in the Czech Republic?

The ÚOOÚ, seated in Prague. Under section 41 of act no. 110/2019 Sb. a breach is reported without undue delay, and a report after 72 hours needs a reason for the delay.

#Does the Czech accessibility act apply to my online shop?

Act no. 424/2023 Sb. covers e-commerce services for consumers and excludes microenterprises. Whether you are in scope is a question for you and the ČOI. I build the interface to work by keyboard and screen reader either way.

#What does the first step cost me?

Nothing. A first written estimate is free of charge. Send the details below.

#Write to me

Send the repository or site URL, what you want done, your deadline and your current PHP and framework version. My reply is written: what I still need from you, and a first estimate that is free. Start on the contact page.

See also in Czech Republic

Need this service: PHP developer in Prague?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Latest PHP developer articles

Oct 21, 2026

PHP2Shell: is my WordPress site at risk and what to do

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released on 21 October 2026, fix two critical vulnerabilities in PHP itself (CVE-2026-109618, CVE-2026-109619). How to check the PHP version in WordPress, what to do when your host has not updated the server yet, and which passwords to change after the update.

Explore other WordPress services and knowledge base