Online retailer in Cluj-Napoca
A shop with a few thousand products leaves shared hosting for a VPS with Redis and queues, then spends its monthly hours connecting stock, e-Factura and the courier API.
PHP and Laravel development in Romania from the team that also hosts your application. We build APIs, back-office systems and WooCommerce stores, modernise PHP 7 codebases and run everything on cPanel or a Docker VPS. The hours included in your plan cover upgrades, security patches and integrations with Romanian invoicing, payment and courier systems.
Most PHP requests fall into three groups. New products in Laravel, with queues for slow jobs, role-based access and versioned database migrations. Older systems that must reach a supported PHP version, or move to Symfony, without a rewrite from scratch. And WooCommerce stores whose theme, checkout or integrations have outgrown their plugins. Every delivery comes with tests on the critical flows, configuration kept apart from secrets and a documented API, so a future developer, yours or ours, can pick the code up without a call.
A brochure site, a WordPress blog or a small Laravel tool runs well on cPanel: LAMP stack, free Let's Encrypt SSL, daily backups and e-mail on the same domain. When you need Redis, queue workers or an exact PHP version per project, we move you to a VPS with Docker and root access. Busy shops and heavy catalogue imports belong on a dedicated server with AMD Ryzen/EPYC or Intel Core/Xeon hardware, NVMe storage and L3/L4 DDoS protection included. Migration from your current provider is free.
PHP projects here rarely stand alone. A shop or back-office usually has to talk to ANAF e-Factura, a payment processor, a courier and an accounting tool, and each link needs queues, retries and an alert when a document sticks. We can wire them directly or through 4invoices and 4conta, which belong to the same ecosystem. Personal data stays in EU data centres under a GDPR Article 28 processing agreement with standard contractual clauses, aligned with ISO 27001 practice and overseen in Romania by ANSPDCP.
You request hours from the DevOps Services section of the client panel and propose the deadline. On PHP projects they usually pay for a major Laravel upgrade, a move from PHP 7 to 8, patches after a WordPress plugin vulnerability or a new integration. The allowance is counted per calendar month and does not roll over, and extra hours are accepted and billed separately by the hour. Larger projects are planned across several months so each month's allowance is used well.
Every plan includes monthly hours of DevOps, CyberSecurity and Programming work delivered by the 4hosting team: 1 h from cPanel Advanced upwards, 1–8 h on VPS, 5–10 h on dedicated servers depending on the plan, and 10 h on GPU servers. You request them from the client panel, unused hours are not carried into the next month, and extra hours are accepted and billed separately.
Raise a request in the client panel, describe what should change in the PHP application and propose the date you need it by.
We read the code and database, estimate the effort in hours, confirm the date and say plainly what fits the monthly allowance and what is billed extra.
Work happens on a separate branch. Tests and migrations run on a copy of production first, then we deploy in a window you have approved.
You receive a changelog, run instructions, configuration variables, the rollback steps and a report of the hours consumed from your allowance.
A shop with a few thousand products leaves shared hosting for a VPS with Redis and queues, then spends its monthly hours connecting stock, e-Factura and the courier API.
A parts distributor gets a Laravel back-office for orders and stock, with supplier price files imported every night and reports split by cost centre.
Booking pages and a WordPress site stay on cPanel Advanced with daily backups, while the included hour covers updates and security checks each month.
Laravel when delivery speed matters and the product must reach users within months. Symfony when the application is large, long-lived and split into strictly separated components. We also pick Symfony more often when taking over an existing enterprise codebase. The choice is made during scoping, not by habit.
We clone production into a test container, run static analysis to find removed or changed features, fix the code and dependencies, then run the test suite. Production switches only when the test environment is green, and the previous image stays ready for an immediate rollback.
A small Laravel app or a WooCommerce store runs on cPanel from the Advanced plan, which also includes one programming hour a month. Once you need Redis, queue workers or a specific PHP version per project, a VPS with Docker is the better home, and we move you without charge.
Usually it is too many plugins, no page or object cache and an oversized database. We trim plugins, add caching, compress images and tune queries. For security we keep core, theme and plugins updated, close the admin area to the public internet and test backup restores instead of assuming them.
Modernise first, in most cases. A rewrite takes months and loses behaviour nobody documented. We inventory the dependencies, add tests around the critical flows, move to a supported PHP version and replace the worst modules one at a time. Rewriting only makes sense when the data model itself is wrong.
Yes, it is one of the most common requests on included hours. We connect to the ANAF API, handle queues and validation errors, keep a message history and alert you when a document stays blocked. Alternatively we connect the application to 4invoices, from the same 4b2b ecosystem.
Tell us what is in production and what needs to change. We estimate in hours and show what your plan already covers.