FAQ – frequently asked questions
Below you'll find answers to the most common questions from clients. If your question isn't answered here — reach out directly.
Below you'll find answers to the most common questions from clients. If your question isn't answered here — reach out directly.
It depends on workload and scope. Most often it starts with a short intro call (within a few days of contact), followed by a 60-minute technical consultation or a scoped proposal. Implementation usually begins within 1–2 weeks of scope approval.
Two models are available: one-off projects with a fixed quote (deployment, migration, integration) and a maintenance subscription (ongoing support, monitoring, development). Details of both models are on the engagement models page.
Yes — subscription-based maintenance gives you: updates, monitoring, backups, fixes and development. This applies to both PrestaShop stores and server infrastructure. The terms are set individually, depending on scale and needs.
Key technologies include PHP (PrestaShop), Python, Node.js/Next.js, Docker, MySQL, Redis, Nginx/Apache, GitLab CI/GitHub Actions and Grafana/Prometheus/Loki for monitoring. The technology stack is always chosen to fit your project — proven tools only.
Yes — all collaboration is fully remote, with companies across Europe, the United States and other international markets. Access is shared securely (SSH, VPN, password manager), and communication takes place via email, video calls and messaging apps.
It starts with your message describing the goal and situation. You receive clarifying questions and then a proposed intro call or technical consultation. After that step you get an action plan with a quote. Once approved — implementation begins.
Every deployment project includes a warranty period. If the issue relates to the implemented changes, it gets fixed under warranty. Audits and consultations do not include a separate implementation warranty. Additionally, with ongoing maintenance you get incident response under an agreed SLA with defined priority and response time.
Yes, a technical consultation is a standalone service. During a 60-minute session you get a diagnosis, clear priorities and an action plan. You can then decide whether to continue or implement changes yourself or with another team.
Reach out directly. You'll get answers to your questions and a clear next step.