# Webdoka - full text of key pages > Full Markdown of key English pages for agents. Short index: https://webdoka.com/llms.txt Generated from site templates. Cached for about 3600 seconds. ## https://webdoka.com/ # Stable web systems. Faster support. Web development & support Stable web systems. Faster support. We build and run web applications for mid-sized companies - from Symfony and Shopware to cloud, outstaffing and AI adoption. [Start a project](https://webdoka.com/contact/) [View services](https://webdoka.com/services/) Symfony Shopware Laravel Vue WordPress Bitrix One team for building, running and evolving your systems. Release pipeline active Deploy ✓ Roadmap Maintenance Stack fit Experience Experience with Symfony, Shopware and other enterprise stacks in mid-sized businesses. Stacks PHP, JS, cloud - the right tool, not the loudest one. Support Maintenance, SLA and outstaffing - when you need extra capacity. Problems → solutions Typical bottlenecks in day-to-day operations - and how we resolve them. Problem A legacy system holds you back Outdated codebases, missing tests, nobody dares to run a deployment. Solution Step-by-step modernisation Refactoring, migration and new modules - without big-bang risk. Problem A shop that does not grow Slow checkouts, weak integrations, features nobody maintains. Solution Shopware / Bitrix e-commerce Scalable shops, payment and ERP integration, measurable conversion gains. Problem No reliable support Tickets go nowhere, hotfixes at midnight, no clear point of contact. Solution Maintenance & SLA Monitoring, priorities, reserved capacity - calm operations. Services Five building blocks - on their own or as one end-to-end setup. [All services →](https://webdoka.com/services/) 01 - DEVELOPMENT Web development Custom applications, APIs and portals. Clean architecture, releases you can trace. Symfony Laravel Vue Angular Node.js Yii [Learn more](https://webdoka.com/web-development/) 02 - E-COMMERCE E-Commerce Shops that sell and keep growing - with integrations that hold up in daily use. Shopware Bitrix WordPress [Learn more](https://webdoka.com/ecommerce/) 03 - MAINTENANCE Maintenance & support Updates, security, performance and incidents - with people you can actually reach. SLA Monitoring Hotfix [Learn more](https://webdoka.com/maintenance/) 04 - CLOUD & TEAM Cloud & outstaffing Infrastructure and extra developer capacity - flexible, without overhead. Cloud Outstaffing DevOps [Learn more](https://webdoka.com/cloud-outstaffing/) 05 - AI ADOPTION AI in business processes Assistants, automation, RAG and CRM integration - with a clear scope instead of hype. Assistants RAG Automation CRM [Learn more](https://webdoka.com/ai/) Technologies We pick stacks to fit the product and the team - not the trend. [All twelve stack pages →](https://webdoka.com/technologies/) Backend Frontend Commerce Cloud & Ops [SymfonyEnterprise PHP, APIs, complex domains](https://webdoka.com/symfony/) [LaravelFast business apps & admin backends](https://webdoka.com/laravel/) [Node.jsRealtime, BFF, microservices](https://webdoka.com/nodejs/) [YiiRobust PHP applications & migrations](https://webdoka.com/yii/) [PythonAutomation, data, AI backends](https://webdoka.com/python/) [FastAPIAPIs, OpenAPI, AI orchestration](https://webdoka.com/fastapi/) [VueProduct UIs, dashboards, SPAs](https://webdoka.com/vue/) [AngularLarge frontends with a clear structure](https://webdoka.com/angular/) [WordPressContent sites, editorial work, landing pages](https://webdoka.com/wordpress/) [HTML/CSSFast, accessible interfaces ShopwareGerman market, B2B/B2C, extensions](https://webdoka.com/shopware/) BitrixPortals, shops, close to CRM [Bitrix24CRM, automation, AI integration](https://webdoka.com/bitrix24/) IntegrationsPayment, ERP, PIM, shipping PerformanceCheckout, caching, observability CloudHosting, containers, scaling CI/CDAutomated deploys & quality OutstaffingDevelopers inside your existing team SupportSLA, on-call, incident response [All technologies](https://webdoka.com/technologies/) How we work Four steps - transparent from the first idea to live operations. 1 Scoping Goals, stack, risks and scope in one short kickoff. 2 Build Iterative deliveries with visible interim results. 3 Handover Docs, access, handover - so your team can carry on. 4 Ongoing care Maintenance, support or outstaffing as needed. Cases Published cases with real numbers. [Read the case study →](https://webdoka.com/cases/webdoka-net/) SaaS · [Laravel](https://webdoka.com/laravel/) · AI [Webdoka.net - SEO SaaS platform](https://webdoka.com/cases/webdoka-net/) Multi-tenant: semantics, rank monitoring, audits, credit billing. Since 2021 · 163 CRM tasks · 1,018 h. Ready for your next release? Tell us briefly what you need - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) Contact Write to us - or call us directly. Start a project For direct enquiries: sales@webdoka.de Website Name Email Company Topic Web development E-Commerce Maintenance & support Cloud & outstaffing AI adoption Technologies / stack Python / FastAPI Something else Message Start a project By submitting you agree to your details being processed in line with our [privacy policy](https://webdoka.com/privacy/). We usually reply within one business day. Thank you. We will be in touch shortly. Reach us directly Phone [+49 176 57730327](tel:+4917657730327) Email [sales@webdoka.de](mailto:sales@webdoka.de) Contact person Dobrusin Jurij Location Tbilisi --- ## https://webdoka.com/web-development/ # Stable systems. Clean releases. [Home](https://webdoka.com/)/ [Services](https://webdoka.com/services/)/ Development 01 - Web development Stable systems. Clean releases. We build web applications, APIs and portals - from the architecture to production operations. Code you can follow, clear modules, releases without drama. [Start a project](https://webdoka.com/contact/) [All services](https://webdoka.com/services/) [Symfony](https://webdoka.com/symfony/) [Laravel](https://webdoka.com/laravel/) [Vue](https://webdoka.com/vue/) [Angular](https://webdoka.com/angular/) [Node.js](https://webdoka.com/nodejs/) [Yii](https://webdoka.com/yii/) [WordPress](https://webdoka.com/wordpress/) [Python](https://webdoka.com/python/) What we deliver Custom software that teams can really operate. Backend & APIs Symfony, Laravel, Yii and Node.js - domain logic, integrations and REST/GraphQL interfaces with tests and CI. Frontends & portals Vue and Angular for data-heavy interfaces. Clear components, with accessibility and performance kept in view. Modernisation Retire legacy stacks step by step - module by module instead of big bang, with measurable milestones. CMS & content hubs WordPress and tailored backends when the editorial team and the product need the same content. How we start A short discovery, then an architecture sketch and a realistic plan - before the first story goes to production. - Scope and risks clarified - in writing and easy to follow - Technical guardrails: stack, deployment, observability - Iterative releases with review and staging - Handover with docs, runbooks and optional maintenance Typical results Customer portals, B2B backends, internal tools, API gateways and microservice splits - always with an eye on running costs. CI/CD Code Review Staging Docs When development is the right call Not every problem needs custom code - and we say so. Good fit Processes that no standard product covers; integrations across several systems; growth with clear requirements on the software. Better done differently A pure content site without logic - then a CMS or shop comes first. We advise honestly and point you to e-commerce or maintenance. Frequently asked questions Short and honest - as in the kickoff. Symfony or Laravel? A complex domain with a long lifetime: often Symfony. A fast business backend with a small team: often Laravel. We settle this before the first sprint. Do you take over existing code? Yes, after a short audit. We name the risks and a realistic cut-off point - even when the answer is “stabilise first”. How do we start a development project? A short discovery, an architecture sketch and a fixed frame before the first story goes to production. Details on the contact page. Do you stay on after launch? Optionally through maintenance and support: runbooks, monitoring and hotfixes - with no knowledge gap between project and operations. Ready for your next release? Describe briefly what you need - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/services/ # Services that last. [Home](https://webdoka.com/)/ Services Five building blocks Services that last. From web development through e-commerce, maintenance and cloud to AI adoption - bookable one by one or as a single continuous setup. [Start a project](https://webdoka.com/contact/) View services Five clusters Choose your entry point - we connect the building blocks when you need them. [01 - DEVELOPMENT Web development Applications, APIs and portals built with Symfony, Laravel, Vue, Angular, Node.js and Yii. Symfony Laravel Vue Node.js Learn more →](https://webdoka.com/web-development/) [02 - E-COMMERCE E-commerce Shopware and Bitrix shops with integrations that hold up in daily use and grow with you. Shopware Bitrix WordPress Learn more →](https://webdoka.com/ecommerce/) [03 - MAINTENANCE Maintenance & support Updates, security, performance and incidents - with people you can reach and clear SLAs. SLA Monitoring Hotfix Learn more →](https://webdoka.com/maintenance/) [04 - CLOUD & TEAM Cloud & outstaffing Infrastructure and extra developer capacity - flexible, without fixed overhead. Cloud Outstaffing DevOps Learn more →](https://webdoka.com/cloud-outstaffing/) [05 - AI ADOPTION AI in business processes Assistants, automation, knowledge search (RAG) and CRM integration - with measurable value. Assistants RAG Automation CRM Learn more →](https://webdoka.com/ai/) How we work Clear scope, releases you can follow, contacts you can actually reach. Product before framework We pick the stack by goal and team - not by trend. The architecture stays maintainable. Transparent handover Documentation, deployment path and knowledge transfer are part of the delivery - not an add-on. Right-sized for mid-market No bloated enterprise processes. Short lines to Dobrusin Jurij and the delivery team. Ongoing care available After go-live: maintenance, SLA or outstaffing - so systems are never “done and abandoned”. Technologies at a glance Twelve stack pages - Symfony to FastAPI. We choose by product and team, not by trend. [Symfony](https://webdoka.com/symfony/) [Shopware](https://webdoka.com/shopware/) [Vue](https://webdoka.com/vue/) [Python](https://webdoka.com/python/) [FastAPI](https://webdoka.com/fastapi/) [All 12 stacks](https://webdoka.com/technologies/) AI adoption is part of it We often orchestrate assistants and RAG with Python/FastAPI - connected to shop, portal and CRM. [AI adoption](https://webdoka.com/ai/) Ready for your next release? Describe briefly what you need - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/ecommerce/ # Shops that sell. [Home](https://webdoka.com/)/ [Services](https://webdoka.com/services/)/ E-Commerce 02 - E-Commerce Shops that sell. Shopware and Bitrix projects with clean integrations to ERP, payment and marketing - built for everyday work in mid-sized companies, not just for launch day. [Start a project](https://webdoka.com/contact/) [All services](https://webdoka.com/services/) [Shopware](https://webdoka.com/shopware/) [Bitrix](https://webdoka.com/bitrix/) WordPress / Woo Commerce services From relaunch to ongoing optimisation. Shopware New stores, migrations and extensions: themes, plugins, checkout flows and B2B features - versioned and testable. Bitrix Bitrix commerce and portals: catalogues, order processes and connections to existing company systems. Integrations ERP, PIM, payment, shipping and CRM - robust interfaces instead of fragile Excel workarounds. Performance & conversion Load times, search and filter journeys, checkout stability - measurable and prioritised by revenue impact. Shopware in focus We know the platform specifics: plugin ecosystem, Rule Builder, Store API and headless options - and when the classic setup is the better choice. Shopware 6 Store API Migration What you can expect - Discovery covering catalogue, checkout and operations - Delivery with staging, data migration and training - Go-live support and intensive aftercare - Optional: maintenance & SLA after launch A good fit if … Relaunch or fresh start The old system holds you back - you need a shop that purchasing and IT can run together. Growth through integrations More channels, more orders, more systems - without reinventing the shop every quarter. Frequently asked questions Short and honest - as in the kickoff. Shopware or Bitrix? B2C/B2B with a broad ecosystem: usually Shopware. An existing Bitrix landscape or close CRM ties: worth checking Bitrix. We compare honestly. Do you migrate data and SEO? Yes - catalogue, customers, orders and the URL plan belong in discovery, before any dates are fixed. Who hosts the shop? Your hosting provider or cloud. We deliver deployment, staging and checks. What happens after go-live? Aftercare and optional maintenance with an SLA - so the launch is not the end of the story. Ready for your next release? Briefly describe what you need - we will come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/shopware/ # Shopware that sells. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Shopware E-commerce - Shopware Shopware that sells. Shops for DACH and international clients - catalogue, checkout and ERP connections that hold up day to day. No theme polishing without operations. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) B2C B2B Migration Plugins ERP Where Shopware fits Retailers and manufacturers who sell across Europe - and whose shop is more than a display window. Migration without downtime Old shop, living catalogue. A big bang over the weekend is not a plan. B2B complexity Price tiers, customer groups, quotes - standard themes tear at this point. Plugin sprawl Twelve extensions, three of them dead. We clear up before we build further. ERP & fulfilment Stock, tracking, invoices. The shop must not be the only source of truth. What we deliver in Shopware Storefront, checkout, integrations - and someone for the time after. Setups & migrations Shopware 6, data transfer, 301 redirects, payments. Live in slices. Plugins & themes Only what the business needs. Custom code where plugins lie. Integrations ERP, PIM, payment, shipping. Queues and monitoring included. Operations Updates, performance, peak checks. Optional SLA through maintenance. Approach: sales before feature lists We start with checkout and stock - not with animations. Whatever keeps revenue running comes first. - Clarify catalogue, payments, shipping and tax - Plugin inventory: keep, replace, remove - Staging with real data, then a cutover plan - Aftercare after go-live, then regular operations Typical environment Shopware 6, custom plugins, a Vue storefront only when it pays off. Often Bitrix or WordPress alongside for content. [E-commerce](https://webdoka.com/ecommerce/) [Bitrix](https://webdoka.com/bitrix/) [Vue](https://webdoka.com/vue/) ERP Payment How a shop project runs From the product range to the first real order. 1 Range & flows Catalogue depth, checkout, returns. What the shop must never get wrong. 2 Build Theme and plugin scope, integrations, test data. 3 Harden Performance, payments in staging, permissions, SEO migration. 4 Live & keep running Cutover, monitoring, support through the first peak week. What retailers rely on Revenue must not turn into a demo. No fake go-live Payments and stock are tested - or we do not go live. European market reality Tax, parcel stations, payment on invoice: we know the market, no US defaults. Ongoing care Updates and incidents after launch - not “good luck”. Example setup (illustrative) Step by step move of a shop to Shopware 6: catalogue and customers first, checkout in the second slice, ERP sync through a queue. Goal: no gap in orders, measurably shorter load time in the listing. [Shopware](https://webdoka.com/shopware/) Migration ERP Checkout Frequently asked questions Questions from real shop kick-offs. Shopware or Bitrix? B2C/B2B with an ecosystem around it: usually Shopware. An existing Bitrix landscape or a close link to CRM: look at Bitrix first. We compare honestly. Shopware 5 to 6? Yes, as a project with a data and plugin plan. Not as an “update click”. Headless? Only if your channels and your team can carry it. Otherwise storefront first. Can you build plugins only? Yes. Or clean up the existing ones. Both are real work. Who hosts it? Your hosting provider or cloud. We deliver deployment and checks. How do we start? Discovery plus a migration outline with a fixed scope. More stacks Related technologies we often use alongside. [E-commerce](https://webdoka.com/ecommerce/) [Bitrix](https://webdoka.com/bitrix/) [WordPress](https://webdoka.com/wordpress/) [Vue](https://webdoka.com/vue/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) Time to switch the shop live? Catalogue size, target shop and time frame are enough for a first proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/maintenance/ # Calm operations. Faster support. [Home](https://webdoka.com/)/ [Services](https://webdoka.com/services/)/ Maintenance 03 - Maintenance & support Calm operations. Faster support. Updates, security, performance and incidents - with people you can reach, clear response times and monitoring that raises the alarm before customers call. [Start a project](https://webdoka.com/contact/) [All services](https://webdoka.com/services/) SLA Monitoring Hotfix Security What the package covers Maintenance is not a parking space for tickets, it is active operations. Updates & patches Framework, plugin and OS updates planned and tested. No “surprise updates” on Friday at 5 pm. Security Hardening, dependency checks and prompt response to CVEs - prioritised by the risk to your system. Monitoring & alerting Uptime, error rates and business checks. Alerts that make sense - and a human at the other end. Incident & hotfix Defined SLAs, escalation paths and post-mortems. So the same fault does not come back three times. An SLA that holds up in daily work We agree response and recovery times that match your risk - not a marketing slide. - A named contact and a backup person - Maintenance windows and a change log - Monthly status instead of silent tickets - Handover from project to operations without losing knowledge Ideal after go-live Whether we built the system or are taking over an existing one: we start with a health check and a priority list. Health check Runbooks On-call Frequently asked questions Short and honest - as in the kickoff. Do you take over systems built by others? Yes. We start with a health check, risks and a priority list - no matter who built the system. Which SLAs do you offer? Response and recovery times that match your risk, in writing. Not a marketing slide. Do you only work with your own stacks? Focus: Symfony, Laravel, Shopware, Bitrix, Vue, WordPress and related PHP and JS landscapes. How do we get started with maintenance? A short conversation, then a health check with a fixed scope. A project request is enough to start. Ready for your next release? Briefly describe what you need - we will come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/cloud-outstaffing/ # Capacity and cloud without overhead. [Home](https://webdoka.com/)/ [Services](https://webdoka.com/services/)/ Cloud & outstaffing 04 - Cloud & outstaffing Capacity and cloud without overhead. Infrastructure that stays deployable - and developers who integrate into your team. Scale flexibly, without fixed costs for capacity you do not use. [Start a project](https://webdoka.com/contact/) [All services](https://webdoka.com/services/) Cloud Outstaffing DevOps Two levers - one partner Cloud operations and team extension from a single source. Cloud & DevOps CI/CD, containers, observability and cost control. Environments where staging really mirrors production. Outstaffing Experienced developers (Symfony, Laravel, Vue, Angular, Node.js, Shopware …) in your board and your rituals - remote and reliable. Team build-up Small teams for temporary peaks: relaunch, migration, feature sprint - with a lead who delivers and communicates. Handover & knowledge transfer We do not only set up the pipeline and the team - we document it so your in-house team can take over. Outstaffing that feels like a team No anonymous ticket workers. Clear seniority, English or German, overlap with EU time zones and a fixed weekly rhythm. How we start - Sharpen the requirement and the skill profile - Short interview or trial week as needed - Onboarding into repo, tools and a shared definition of done - Monthly review of pace, quality and team fit Stacks for team extension Symfony Laravel Vue Angular Node.js Yii Shopware Bitrix WordPress Cloud / DevOps Frequently asked questions Short and honest - as in the kickoff. Outstaffing or a fixed project? Team extension if you already have rituals and a backlog. A fixed project if the scope is clear and we should deliver. Both work - but not mixed without clear roles. Which time zones do you cover? Overlap with European working hours. Daily and weekly meetings in your rhythm, in English or German. Which cloud do you use? Whatever your operations and budget can carry - your hosting provider or containers in the cloud. We set up CI and observability without infrastructure dogma. Is there a minimum term? After onboarding usually cancellable on a monthly basis, unless agreed otherwise. We clarify the details in a call. Ready for your next release? Briefly describe what you need - we will come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/ai/ # AI that works day to day. [Home](https://webdoka.com/)/ [Services](https://webdoka.com/services/)/ AI adoption 05 - AI adoption AI that works day to day. We bring assistants, automation and knowledge search into your existing processes - connected to CRM, documents and line-of-business systems. With a clear scope and measurable value. [Start a project](https://webdoka.com/contact/) [All services](https://webdoka.com/services/) Assistants Automation RAG CRM [Python](https://webdoka.com/python/) [FastAPI](https://webdoka.com/fastapi/) Who this fits Mid-sized companies and teams that already run their processes digitally - and lose hours to repetition. Support & back office The same questions over and over, long waiting times, knowledge stuck in people's heads and tickets - not in a system. Sales & CRM Leads, notes and follow-ups are spread across tools. Status is missing, and the wrap-up costs hours. Specialist departments Policies, manuals and legacy documents are all there - but nobody finds the right passage quickly. IT & product Pilot chatbots with no link to real data. We connect models to your systems - including rules and governance. What we deliver Building blocks you can book on their own or as one end-to-end setup. AI assistants Internal or customer-facing assistants for FAQs, quoting support, onboarding and specialist questions - with clear limits and logging. Process automation Classification, summaries, routing and wrap-up for tickets, emails and forms - wired into your workflows. RAG & knowledge search Retrieval across manuals, contracts, wikis and tickets - answers with sources instead of unsupported generalities. CRM & system integrations Connections to Bitrix24, Shopware, Symfony/Laravel backends and APIs - so AI works where the work happens. Approach: value before model choice We start with the process and the data - not with the loudest model. The architecture stays maintainable; cost and data protection are part of the plan. - Use case and success metric put down in writing - Data sources, permissions and PII boundaries clarified - Pilot with staging, evaluation and a fallback path - Handover with runbooks, monitoring and optional maintenance Typical stack Python and FastAPI for orchestration and APIs; an embedding/RAG pipeline; integration with existing PHP/JS systems and CRM. [Python](https://webdoka.com/python/) [FastAPI](https://webdoka.com/fastapi/) RAG Bitrix24 OpenAI / Azure Self-hosted optional How adoption runs Four steps - from workshop to stable operation. 1 Scoping Workshop: processes, data, risks, quick wins. Result: a prioritised use case list and a rough business case. 2 Pilot A narrow slice on staging: prompting/RAG, integration, evaluation against real examples from your daily work. 3 Integration CRM, tickets, documents and permissions. Observability, cost limits and human-in-the-loop where needed. 4 Operation Go-live, training, metrics. Optional: maintenance, model updates and a rollout to further processes. What you can build on As pragmatic as our development and maintenance work - only with AI building blocks. No black box pilot You see the architecture, the data flows and the cost frame - before anything goes “live”. Integration, not a demo We plug into CRM and line-of-business systems - not just a chat UI without context. Ongoing support available After go-live: monitoring, prompt and index upkeep, SLA - the same as in our maintenance packages. Example setup (sample case) Internal assistant for support teams: RAG across the knowledge base and ticket history, connected to Bitrix24, escalation to people whenever confidence is low. Target metrics: faster first response, fewer repeated follow-up questions, traceable sources. RAG Bitrix24 FastAPI Human-in-the-loop Frequently asked questions Short and honest - the way we talk in a kickoff. Do we need our own LLM? Usually not. Many use cases run on API models plus RAG and a clean integration. We look at self-hosting when data protection, latency or cost call for it. What about data protection and GDPR? We clarify data classes, processing agreements and storage locations before the pilot. Sensitive fields can be masked, excluded or processed on-premises only. How quickly do we see value? Typically a measurable pilot within a few weeks (one clear task, one channel, one metric). Scaling follows once the pilot holds - not before. Does AI replace our team? No. The point is to take repetition and searching off people - decisions and escalations stay with humans wherever quality matters. Can you connect to existing Symfony, Shopware or Bitrix systems? Yes. That is exactly where we start: APIs, webhooks, CRM fields and existing auth - instead of a parallel island solution. What does it cost to get started? After a short discovery we name a fixed budget for the workshop and the pilot. No open-ended invoices without a scope. We clarify the details under [Contact](https://webdoka.com/contact/). Ready for your next AI step? Describe briefly which process you want to unload - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/technologies/ # Technologies we run. [Home](https://webdoka.com/)/ Technologies Twelve stacks Technologies we run. We choose stacks by product and team - not by trend. Each page explains who the stack fits, what we deliver and how the first step looks. [Start a project](https://webdoka.com/contact/) [Services](https://webdoka.com/services/) All stacks Twelve SEO pages - abstract marks, no trademark logos. Click through to the entry point that fits you. Backend [Symfony Enterprise PHP, APIs, complex domains Learn more →](https://webdoka.com/symfony/) [Laravel Business apps, admin panels, rebuilds Learn more →](https://webdoka.com/laravel/) [Yii Legacy systems, stabilisation, migration Learn more →](https://webdoka.com/yii/) [Node.js BFF, realtime, lean services Learn more →](https://webdoka.com/nodejs/) [Python Automation, data, AI backends Learn more →](https://webdoka.com/python/) [FastAPI APIs, OpenAPI, AI orchestration Learn more →](https://webdoka.com/fastapi/) Frontend & content [Vue Product UIs, dashboards, SPAs Learn more →](https://webdoka.com/vue/) [Angular Large frontends with a clear structure Learn more →](https://webdoka.com/angular/) [WordPress Content hubs, editorial work, landing pages Learn more →](https://webdoka.com/wordpress/) Commerce & CRM [Shopware DACH shops, B2B/B2C, integrations Learn more →](https://webdoka.com/shopware/) [Bitrix Portals, shops, close to CRM Learn more →](https://webdoka.com/bitrix/) [Bitrix24 CRM, automation, AI integration Learn more →](https://webdoka.com/bitrix24/) How we choose Product before framework. The stack has to fit the team and the runtime. Existing systems count A running Yii or Bitrix system is not a flaw. We harden and open it up before selling a rewrite. The edges may be new Python, FastAPI and Node.js often sit next to PHP - for AI, BFF and automation. Commerce is its own case Shopware for DACH shops, Bitrix when the landscape already lives there. WordPress stays a CMS, not an ERP. Operation afterwards Every stack we recommend, we can also maintain - updates, SLA, incidents. Services alongside Technologies are tools. What you book are clusters: development, shop, maintenance, cloud or AI adoption. [Development](https://webdoka.com/web-development/) [E-commerce](https://webdoka.com/ecommerce/) [Maintenance](https://webdoka.com/maintenance/) [Cloud](https://webdoka.com/cloud-outstaffing/) [AI adoption](https://webdoka.com/ai/) Not sure which stack? Send us the goal, the existing system and the team size - we answer with an honest recommendation, not with a feature matrix. [Start a project](https://webdoka.com/contact/) Ready for your next release? Stack, goal, timeline - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/symfony/ # Symfony for complex domains. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Symfony Backend - Symfony Symfony for complex domains. Enterprise PHP, APIs and portals - with clear bundles, tests and a deploy path your team can actually run. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) APIs Portals DDD-lite Messenger PHPUnit Where Symfony fits When rules, integrations and lifespan reach further than a seasonal shop. B2B portals & domain logic Pricing rules, permissions, approvals and history - a standard CMS hits its limits here quickly. Legacy systems Symfony apps that grew without tests and without clear modules. We carve them up instead of reinventing them. API-first teams Several frontends, partners and mobile need stable contracts - not one UI that drags everything along. IT under compliance pressure Auditable releases, traceable auth and logging belong in the scope, not in an addendum. What we deliver in Symfony From the first slice to handover - operations included. APIs & integrations REST or messaging to ERP, CRM and line-of-business systems. Contracts, versioning, error paths. Domain modules Clear bounded contexts instead of monolithic controllers. Bundles only where they really share something. Queues & jobs Messenger, retries, dead-letter - so imports and mail do not block the request. Quality & CI PHPUnit, static analysis, staging and review. No “hotfix on prod, we will look tomorrow”. Approach: architecture before magic We use Symfony as a tool - not as a religion. Fewer bundles, more explicit modules. What the team cannot explain does not go to production. - Read the existing code and the risks before stacking features - Define the slice: modules, auth, deploy, observability - Deliver iteratively - with tests on the expensive edges - Handover with docs, runbooks and optional maintenance Typical environment PHP 8, Symfony 6/7, Doctrine, Messenger. Frontend often Vue or Twig. Operations through CI and staging. [Vue](https://webdoka.com/vue/) [Laravel](https://webdoka.com/laravel/) [Node.js](https://webdoka.com/nodejs/) Doctrine CI/CD How a Symfony project runs Four steps - from the audit to stable operations. 1 Read Code, data flows, pain. Result: a sketch of the slice and the risks, not 80 slides. 2 Slice First module or API slice on staging - including auth and test data. 3 Harden Observability, jobs, permissions. Performance on the real bottlenecks, not on synthetic micro-benchmarks. 4 Hand over Docs, deploy, knowledge transfer. Optional: an SLA through maintenance. What you can build on Enterprise-ready - without the overloaded enterprise effort. Upgradeable We plan Symfony upgrades as work, not as a surprise three major versions later. Fits your team Code your developers can read. No opaque bundles without an owner. Ongoing care After go-live: hotfixes, security and releases - in line with our maintenance packages. Example setup (illustrative) B2B customer portal: tiered pricing, approval workflow, ERP connection. Symfony API, Vue frontend, Messenger for catalogue sync. Goal: less manual rework, traceable orders. [Symfony](https://webdoka.com/symfony/) [Vue](https://webdoka.com/vue/) ERP Messenger Frequently asked questions Honest - as in the kickoff. Symfony or Laravel? Complex domain, long lifespan, several teams: often Symfony. A fast business backend with a small team: often Laravel. We say which one before the first sprint. Can you lift an old Symfony 3/4? Yes - step by step. Tests and deploy first, then the components. No big-bang rewrite without evidence. Flex, bundles, DDD - do we need all of it? Only what the case carries. DDD-lite where rules are expensive. Bundles are not a status symbol. Do you take over existing code? Yes, after a short audit. We name the risks and a realistic slice - even when the answer is “stabilise first”. What does hosting look like? We work with your cloud or your hosting provider. We set up containers and CI without infrastructure dogma. What does it cost to start? After discovery, a fixed scope for the audit plus the first slice. Details under contact. More stacks Related technologies we often use alongside. [Laravel](https://webdoka.com/laravel/) [Yii](https://webdoka.com/yii/) [Vue](https://webdoka.com/vue/) [Web development](https://webdoka.com/web-development/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) Ready for the next Symfony slice? Describe briefly which portal or which API you need - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/laravel/ # Laravel that ships. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Laravel Backend - Laravel Laravel that ships. Business apps and admin backends with clear modules, queues and a staging that is more than just “somehow there”. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) Business apps Admin APIs Queues Rebuilds Where Laravel works Mid-sized companies that need pace - without building the next legacy monolith. Internal tools & admin Excel and email as an operating system. You need permissions, lists, exports - and someone who maintains it. Rebuild instead of patchwork Old PHP app, no tests, deploys over FTP. We replace it module by module. Small product teams Laravel gives you pace. We keep that pace without magic that nobody can explain later. APIs for apps & partners Sanctum/Passport, clear resources, versioning - so mobile does not stick to the backend. What we deliver in Laravel From the first endpoint to the runbook. Backends & APIs Domain logic, REST, jobs. Policies instead of if-trees scattered everywhere. Admin interfaces Tailored back-office UIs - not a plugin zoo that nobody owns. Integrations Payment, ERP, CRM, mail, files. With retries and visible errors. Rebuild paths Step-by-step replacement: the new Laravel app alongside, traffic moved gradually, data migrated cleanly. Approach: pace with guardrails Laravel is fast. We make it durable: explicit modules, tests on the expensive edges, no “one service with 40 methods”. - Scope and success criteria in writing - Stack guardrails: auth, queue, deploy, logs - Weekly slices on staging - Handover including docs and optional maintenance Typical environment Laravel 10/11, PHP 8, queues, Vue or Blade. CI with tests. Optionally Horizon and Scheduler. [Vue](https://webdoka.com/vue/) [Symfony](https://webdoka.com/symfony/) [Node.js](https://webdoka.com/nodejs/) Queues CI/CD How a Laravel project runs Clarify briefly, then deliver visibly. 1 Clarify Users, data, integrations. What can wait - and what cannot. 2 First slice One end-to-end flow on staging: login, core action, deploy. 3 Go deeper Jobs, permissions, reports. Performance where lists and exports hurt. 4 Hand over Docs, access, runbook. Optionally we keep looking after it. What you can build on Fast - but not sloppy. No framework lock-in as an excuse We document what Laravel handles and what belongs to your domain. Rebuild without a big bang Old and new world side by side until the cut holds. People behind the tickets Dobrusin Jurij stays in the loop - not just a board. Example setup (illustrative) Legacy admin system replaced step by step: orders and customers move into the Laravel backend, the old interface stays for reports at first. Goal: shorter deploy cycles, tests on pricing and permission rules. [Laravel](https://webdoka.com/laravel/) Replacement Queues Staging Frequently asked questions Short answers, as in a conversation. Laravel instead of Symfony? Yes, when the team is small and the product is mostly CRUD plus a few hard edges. With a very long lifespan and many contexts we check Symfony. Filament, Nova, custom admin? Whatever the team can maintain. Often a custom light admin instead of a third ecosystem. Do you take over existing Laravel apps? Yes. First an audit (tests, deploys, secrets), then a plan. How do you keep Eloquent in check? Clear aggregates, query objects in the expensive places, no N+1 surprises in lists. Hosting? Forge-like, containers or your own hosting provider. We set up CI and stay honest about costs. Cost to start? A fixed scope after a short discovery. The contact form is enough. More stacks Related technologies we often use alongside. [Symfony](https://webdoka.com/symfony/) [Vue](https://webdoka.com/vue/) [Yii](https://webdoka.com/yii/) [Web development](https://webdoka.com/web-development/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) Ready for your next Laravel release? Stack, goal, timeframe - we answer with a concrete cut. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/yii/ # Yii - robust and honest. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Yii Backend - Yii Yii - robust and honest. We keep Yii applications running, add APIs and migrate when the business case carries it - not for the sake of a trend. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) Yii 2 Migration Stabilisation APIs Where Yii still counts Plenty of line-of-business systems are running. They need operations and a way out - not a trend presentation. Yii 1/2 legacy Code that is years old, few tests, and the one colleague who “knows the system”. Domain logic in the controller Rules sit in actions and views. We pull them out before we stack features on top. Connecting to the outside New shops or apps need APIs. The Yii system stays the source of truth - for now. Migration pressure Management wants Laravel or Symfony. We check what really pays off. What we deliver Stabilise, open up, migrate if it is worth it. Stabilisation Security updates, PHP version, deploy, monitoring. First breathe, then build. API layer REST in front of the legacy system - so new UIs do not sink into the old view layer. Targeted features New modules in the project's own Yii style, not as a third framework alongside. Migration path If it pays off: step-by-step migration to Laravel or Symfony, with data and cutover planned. Approach: respect what is there Yii is not a flaw. An uncontrolled rewrite often is. We measure risk, cost and benefit - and we also say “not yet”. - Inventory: modules, data, hidden jobs - Lift the security and PHP level - One new channel (API) instead of a big bang - Migration only with a business case and a rollback Typical environment Yii 2, MySQL/Postgres, PHP 8 where possible. Target stack often Laravel or Symfony, frontend Vue. [Laravel](https://webdoka.com/laravel/) [Symfony](https://webdoka.com/symfony/) [Vue](https://webdoka.com/vue/) APIs How we proceed No big-bang rewrite in week one. 1 Inventory What runs, what hurts, who operates it. Risks in writing. 2 Harden Updates, backup, staging. Only then new features. 3 Open up An API or a new module with tests. 4 Decide Stay on Yii or migrate step by step - with numbers, not with slides. What you can build on Honest about the technology - loyal to operations. No forced migration We do not earn money by talking Yii down. Keep the knowledge Docs and pairing before the last expert leaves. One point of contact Development and operations from one team. Example setup (illustrative) Industry solution on Yii 2: PHP and security lifted, REST for a new Vue frontend, core bookings stay in the legacy system. Migration decision after three months of operation - not on kickoff day. [Yii](https://webdoka.com/yii/) [Vue](https://webdoka.com/vue/) API Staging Frequently asked questions The questions teams really ask. Is Yii still worth it? For existing systems: yes, if stability and costs add up. For greenfield: rarely our first choice. Yii 1 to 2, or off it altogether? It depends on tests, data and expected lifespan. We cost out both routes. Can you just “keep it alive”? Yes - maintenance and hotfixes, with no pressure to modernise. Where do you usually migrate to? Laravel or Symfony, depending on team and domain. Frontend often Vue. How long does an inventory take? Usually a few days up to two weeks - enough for an honest plan. How do we start? An audit package with a fixed scope. Getting in touch is enough. More stacks Related technologies we often use alongside. [Laravel](https://webdoka.com/laravel/) [Symfony](https://webdoka.com/symfony/) [Maintenance](https://webdoka.com/maintenance/) [Web development](https://webdoka.com/web-development/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) Time to clarify your Yii legacy? Write to us with the version and the pain - we will propose an inventory or a hotfix. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/bitrix/ # Bitrix without ballast. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Bitrix E-commerce & portals - Bitrix Bitrix without ballast. Portals and shops tied to CRM and business processes - tidy, integrated, operable. No module sprawl. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) Portals Shops Close to CRM Integrations Where Bitrix fits When the portal, the shop and internal processes already live in one landscape. Portals that grew over years Permissions, intranets, catalogues - all in one instance, nobody knows every module. Shop plus CRM Orders should land in the same world as leads. Broken handovers between systems cost time. Fear of updates Years without a core update. We plan the route instead of hoping. Pressure to move to Shopware “Everyone is moving to Shopware.” Sometimes right - sometimes more expensive than stabilising. What we deliver in Bitrix Clean up, connect, operate. Portal & shop Catalogue, order flows, internal areas. Only the modules that someone owns. Integrations Payment, ERP, shipping, Bitrix24. Visible errors instead of silent dead syncs. Stabilisation Updates, performance, permissions audit, staging. Migration advice Honestly: stay, split, or move towards Shopware - with a cost picture. Approach: landscape first Bitrix is strong when processes already live there. We do not fight the product - we cut the ballast away. - Module and permissions inventory - Harden critical flows (checkout, portal login) - Make integrations visible - Define operations and the update path Typical environment A Bitrix site, often Bitrix24 alongside. Vue for frontend parts where it makes sense. Alternative or successor: Shopware. [Bitrix24](https://webdoka.com/bitrix24/) [Shopware](https://webdoka.com/shopware/) [E-commerce](https://webdoka.com/ecommerce/) ERP How we work No greenfield fairy tale when the existing system carries the business. 1 Inventory Modules, users, integrations, pain points. 2 Harden Staging, updates, the three most expensive bugs. 3 Connect One clear sync or one new flow. 4 Keep or switch An operations package or a migration outline. What you can rely on No Bitrix propaganda. An honest alternative If Shopware fits better, we say so - and then we build Shopware. Operations, not a demo We also take over the legacy system nobody loves. Short lines English and German speaking, close to the owner, Tbilisi and remote. Example setup (illustrative) Manufacturer portal: dealer login, catalogue, ordering in Bitrix; sync to ERP; content pages slimmed down. Goal: fewer manual orders, an update path for the coming year. [Bitrix](https://webdoka.com/bitrix/) Portal ERP Staging Frequently asked questions Plain answers about a contested stack. Is Bitrix still a current choice? As an existing landscape: yes, if it runs. As a greenfield shop in Europe: often Shopware. Decide by what you already operate, not by forum posts. Bitrix and Bitrix24 - the same thing? No. Site and shop versus CRM. We keep them apart in the proposal and in operations. Can you catch up on core updates? Yes, planned, with staging and rollback. Not “quickly on a Friday evening”. Migration to Shopware? Possible. We estimate data, SEO and plugin replacements before we promise dates. Who supports it afterwards? We do - through maintenance & support. How do we start? An inventory workshop with a fixed scope. More stacks Related technologies we often use alongside. [Bitrix24](https://webdoka.com/bitrix24/) [Shopware](https://webdoka.com/shopware/) [E-commerce](https://webdoka.com/ecommerce/) [Maintenance](https://webdoka.com/maintenance/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) Sort out your Bitrix landscape? Instance, pain, goal - we tell you whether hardening or switching is the better work. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/bitrix24/ # Bitrix24 that really works. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Bitrix24 CRM - Bitrix24 Bitrix24 that really works. CRM, automation and integrations - so that leads, orders and follow-up work do not sink into chats. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) CRM Automation Pipelines AI integration Where Bitrix24 counts Sales and back office teams that already have a CRM - but do not use it as a system. CRM as a notebook Leads in Excel, status in someone's head, Bitrix24 used as a chat. A pipeline without truth. Shop without a return channel Orders never become deals. Support cannot see the customer. Automation that annoys Robots without an owner. We build a few that someone understands. AI without context A chatbot without CRM fields. We connect assistants to real data - see AI adoption. What we deliver in Bitrix24 Processes first, apps second. Pipelines & fields Stages, required fields, permissions. Less cosmetics, more control. Automation Robots for follow-up, escalation and tasks - with an off switch and logging. Integrations Shopware, a Bitrix shop, mail, telephony, your own APIs. AI integration Assistants and RAG through FastAPI that read and write CRM context - under control. Approach: process before app marketplace We do not install “another 12 apps”. We model the sales or service process and automate what repeats. - Map the current process and the gaps between systems - Define the pipeline and the data quality - One automation or one integration first - Training, permissions, operations Typical environment Bitrix24 cloud or on-prem. Connected to Shopware or Bitrix. AI part through Python/FastAPI. [AI](https://webdoka.com/ai/) [Shopware](https://webdoka.com/shopware/) [FastAPI](https://webdoka.com/fastapi/) [Bitrix](https://webdoka.com/bitrix/) How we introduce or rework Bitrix24 No second CRM next to the first one. 1 Listen Who sells, who serves customers, where data dies. 2 Model One pipeline, few fields, clear owners. 3 Connect Shop or mail, then automation. 4 Keep it running Training, hygiene rules, optional AI pilot. What you can rely on CRM as a tool, not as a religion. No app overload Every add-on has an owner or it goes. Integration instead of a demo We measure whether deals really appear. AI with guardrails No autonomous emails without approval, if you do not want that. Example setup (illustrative) Back office: enquiries from shop and mail become deals, follow-up runs automatically, escalation goes to people. An optional assistant reads the knowledge base (RAG) and suggests answers - with the source. [Bitrix24](https://webdoka.com/bitrix24/) [AI](https://webdoka.com/ai/) [FastAPI](https://webdoka.com/fastapi/) Automation Frequently asked questions Practical, not written like an advert. Cloud or on-prem? Whatever data protection and your IT require. We work with both, on-prem needs clear operations. Do you replace Salesforce or HubSpot? Only if the case supports it. Often Bitrix24 is already in place - then we use it. Can you just install apps? We can. Usually the sensible move is a process plus one integration. AI in the CRM - is it safe? With data classes, logging and a human in the loop. Details on the AI page. Migration from Excel? Yes: fields, import, training. The hardest part is habit, not CSV. How do we start? A workshop plus one pipeline. Fixed scope after the first call. More stacks Related technologies we often use alongside. [AI adoption](https://webdoka.com/ai/) [Bitrix](https://webdoka.com/bitrix/) [Shopware](https://webdoka.com/shopware/) [FastAPI](https://webdoka.com/fastapi/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) A CRM that keeps up? Describe your pipeline and the gaps - we propose the first slice of automation. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/vue/ # Vue interfaces that stay clear. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Vue Frontend - Vue Vue interfaces that stay clear. Dashboards, portals and SPAs - components a team can keep building on. Not a frontend that nobody touches after 18 months. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) SPA Dashboards Design system APIs Where Vue fits Products with dense interfaces - not every brochure site needs an SPA. Data-heavy UIs Tables, filters, permissions, live status. Sprawling jQuery or a legacy frontend nobody likes. Portal next to an API The Symfony or Laravel backend is in place. The interface is not. Design without a system Every page a one-off. We bring in tokens and components. Performance & A11y Heavy bundles, no keyboard support. Both are deliverables. What we deliver in Vue From the first route to a Storybook-style structure. SPAs & portals Vue 3, Router, clear stores. Only as much state as the flow needs. Dashboards Lists, charts, bulk actions - with empty and error states. Design systems A small component library instead of copy-paste. Integration BFF or direct API. Auth, uploads, optimistic UI where it helps. Approach: the interface as a product Vue is the glue, not the star. We cut along user jobs: one task, one flow, measurable. - Clarify the key jobs and permissions - Lock down API contracts with the backend - Components and states (empty, loading, error) - Handover: build, tokens, short docs Typical environment Vue 3, Vite, often Pinia. Backend Symfony, Laravel or FastAPI. Occasionally Nuxt for content plus app. [Symfony](https://webdoka.com/symfony/) [Laravel](https://webdoka.com/laravel/) [Angular](https://webdoka.com/angular/) [Node.js](https://webdoka.com/nodejs/) How we build frontends Visible, iterative, no pixel polishing without data. 1 Flows Three core tasks, not 40 screens at once. 2 Structure Components plus a dummy API, then real data. 3 Hardening A11y, performance, permissions, empty lists. 4 Handover Build pipeline, tokens, optional maintenance. What product teams rely on A frontend that does not embarrass the backend. No framework by reflex Sometimes Twig or Blade is enough. We say so. Integration taken seriously We do not build against an imaginary API. Ready to be extended Your people should be able to commit on their own after two weeks. Example setup (illustrative) Dealer portal: orders, invoices, account blocks. Vue 3 on a Symfony API. Goal: fewer Excel exports, traceable permissions, usable on a tablet in the warehouse. [Vue](https://webdoka.com/vue/) [Symfony](https://webdoka.com/symfony/) Portal A11y Frequently asked questions Frontend questions without trend promises. Vue or Angular? Small to mid-size product UIs: often Vue. Large enterprise frontends with a fixed team split: Angular. We choose by team, not by social media trends. Nuxt? When SEO and app come together. Otherwise a Vite SPA behind auth. Do you take over Vue 2 code? Yes - we plan the migration to 3 as work, not as a big-bang day. Who does the design? We implement and refine it. We do not invent a greenfield brand identity without a brief. SSR, i18n, tests? Where the case calls for it. Tests on the expensive flows, not for the sake of coverage. How do we start? One flow in staging. Fixed scope after kickoff. More stacks Related technologies we often use alongside. [Angular](https://webdoka.com/angular/) [Symfony](https://webdoka.com/symfony/) [Laravel](https://webdoka.com/laravel/) [Web development](https://webdoka.com/web-development/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) An interface that holds? Tell us the API and the most important user job - we will sketch the first slice. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/angular/ # Angular for large frontends. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Angular Frontend - Angular Angular for large frontends. Structured UIs for teams that stay with the same product for years - modules, standards, no "everyone brings their own framework". [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) Enterprise UI Modules RxJS Design system Where Angular pays off Large interfaces, several teams, a long lifespan. Enterprise portals Many roles, many modules, compliance. Vue would work too - structure is the win here. Grown Angular apps Old version, nobody dares to upgrade. We raise it step by step. Several squads Without conventions every feature turns into a dialect. We set the guard rails. Heavy data flows Streams, polling, offline edges. RxJS with discipline, not as a sport. What we deliver in Angular Architecture that survives reviews. Module boundaries Lazy routes, clear APIs between features, shared code only where sharing is honest. Upgrades Major versions in steps, tests on the critical flows. Design systems Internal library, tokens, consistent forms. Integration REST/BFF, auth, interceptors, error and empty states. Approach: conventions over personal style Angular pays off when the team uses the rails. We write the rails down - and stick to them ourselves. - Read the existing code and version honestly - Target architecture and a short style guide - One feature module as the pattern - An upgrade or expansion path Typical environment Current Angular, often Nx with several apps. Backend Symfony, non-.NET stacks or a Node.js BFF. [Vue](https://webdoka.com/vue/) [Node.js](https://webdoka.com/nodejs/) [Symfony](https://webdoka.com/symfony/) CI/CD How we deliver Angular Pattern first, then breadth. 1 Audit Version, bundle, the three painful modules. 2 Pattern One feature built to the target architecture. 3 Breadth Further modules or upgrade steps. 4 Handover Docs, lint, CI, pairing with your team. What you can rely on Built to last - not "rewrite in two years". Upgrades as work We plan major versions instead of fearing them. Team fit Pairing and reviews, so the knowledge does not stay with us. An honest alternative If Vue is enough, we recommend Vue. Example setup (illustrative) Internal control frontend: roles, approvals, audit log. Angular upgrade plus module boundaries. Goal: shorter feature cycles, manageable bundles. [Angular](https://webdoka.com/angular/) Upgrade Modules CI Frequently asked questions Structural questions, answered briefly. Isn't Angular heavy? A steeper start, a clear win on large UIs. For landing pages it is the wrong tool. Signals, RxJS, NgRx? As much state library as the case needs. Not every list is a global store. Nx? When there are several apps and libraries. Otherwise the standard CLI. Can you upgrade an existing Angular 8/12? Yes, step by step, with tests on the expensive routes. Who writes the backend? We do, or your team. Contracts first. How do we start? An audit plus a sample module. Fixed scope. More stacks Related technologies we often use alongside. [Vue](https://webdoka.com/vue/) [Node.js](https://webdoka.com/nodejs/) [Symfony](https://webdoka.com/symfony/) [Web development](https://webdoka.com/web-development/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) A frontend with rails? Version, team size, pain points - we suggest an audit or a feature slice. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/nodejs/ # Node.js for speed and realtime. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Node.js Backend - Node.js Node.js for speed and realtime. BFF, events and lean services - where PHP is not the right process. No "everything in Node.js because it is a trend". [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) BFF Realtime Services Queues Where Node.js makes sense When the edge is about live data, aggregation or a JavaScript team. BFF for SPAs Vue/Angular should not orchestrate twelve PHP endpoints. A BFF tidies that up. Realtime Status, chat, collaboration. We replace constant polling where it pays off. Micro slices One service for webhooks or PDFs - not the next monolith in green. JS-heavy teams One stack less to keep in mind. We still keep clear boundaries to the domain. What we deliver in Node.js Lean, observable, replaceable. BFF & APIs Aggregation, auth pass-through, caching. OpenAPI where it helps. Realtime WebSocket or SSE - with fallbacks and load limits. Workers Queues, webhooks, file jobs. Visible retries. Platform CI, containers, logs, health checks. No laptop deploys. Approach: Node.js as an edge, not as the whole world Many of our clients stay on Symfony or Laravel. Node.js sits in front of it or next to it - clearly scoped. - Define the job of the edge (BFF, event, worker) - Write the contracts towards PHP/Python services - Build in observability and limits - Handover with a runbook Typical environment Node.js 20+, often TypeScript, Fastify/NestJS only if the team can carry it. Alongside Vue/Angular and PHP APIs. [Vue](https://webdoka.com/vue/) [Angular](https://webdoka.com/angular/) [FastAPI](https://webdoka.com/fastapi/) [Laravel](https://webdoka.com/laravel/) How we scope Node.js services One job, one process, clear owners. 1 Define the edge What Node.js may do - and what stays in PHP. 2 Slice One endpoint or one socket flow in staging. 3 Hardening Auth, rate limits, load, dead letters. 4 Operations Metrics, alerts, docs. What you can rely on No quiet change of platform. The boundary holds We do not quietly move the whole domain into Node.js. TypeScript in moderation Types on the contracts, not 200 utility files. Ongoing support On-call available through maintenance. Example setup (illustrative) BFF in front of a Vue dealer portal: aggregates Symfony APIs, caches listings, pushes status via SSE. Goal: fewer roundtrips, noticeably faster lists. [Node.js](https://webdoka.com/nodejs/) [Vue](https://webdoka.com/vue/) [Symfony](https://webdoka.com/symfony/) BFF Frequently asked questions Without runtime holy wars. Why not everything in PHP? Some edges are more honest in Node.js: BFF, realtime, JS tooling. The domain can stay in PHP. Nest, Express, Fastify? Whatever your team maintains. We prefer lean over enterprise appearance. Is TypeScript mandatory? For public contracts, yes. For an 80-line worker, negotiable. Serverless? When load and cost fit. Otherwise a small service in the cluster. Do you take over existing Node.js code? Yes, after an audit (dependencies, secrets, event loop sins). How do we start? One BFF slice or one worker. Fixed scope. More stacks Related technologies we often use alongside. [Vue](https://webdoka.com/vue/) [FastAPI](https://webdoka.com/fastapi/) [Symfony](https://webdoka.com/symfony/) [Web development](https://webdoka.com/web-development/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) A clear Node.js edge? Tell us what has to be live or aggregated - we propose the smallest service that makes sense. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/python/ # Python for data, automation and AI. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ Python Backend & AI - Python Python for data, automation and AI. Scripts, pipelines and services that take load off your core systems - from imports to RAG. No notebook that nobody ever puts into production. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) Automation Pipelines AI APIs Data When Python is the right lever When the PHP applications should stay as they are - and there is work next to them that fits Python more honestly. Repetition CSV imports, reports, reconciliations. At night, error-prone, in one person's head. Knowledge & documents The manuals and tickets are there - nobody finds the right passage. This is where AI and RAG start. Data pipelines Several sources, messy fields, no owner. We build jobs you can see. Model integration A pilot chat with no systems behind it. We orchestrate models behind your processes. What we deliver in Python From automation to the AI backend. Automations Imports, reconciliations, notifications. Logging and retries included. Pipelines Cleaning, features, delivery - as a job, not as a laptop script. AI building blocks RAG, classification, summarisation. See AI adoption. Services Often behind FastAPI. Connected to Bitrix24, Shopware, Symfony. Approach: value before notebook We start with the task and the data permissions. The model or the library is the second decision. - Task, data class, success criterion - Job or API - deliberately small - Staging, evaluation, fallback - Operations: logs, costs, owner Typical environment Python 3, often FastAPI, jobs in queues. Models via API or self-hosted. PHP systems remain the system of record. [FastAPI](https://webdoka.com/fastapi/) [AI](https://webdoka.com/ai/) [Bitrix24](https://webdoka.com/bitrix24/) [Shopware](https://webdoka.com/shopware/) How Python reaches everyday work No research project without acceptance. 1 Task Which hour do we want to buy back? 2 Data Sources, permissions, PII. What may the script see? 3 Pilot One job or one endpoint in staging, against real examples. 4 Operations Schedule, alerts, runbook. Maintenance optional. What business teams rely on Python as craft, not as a show. Integration first We write into your systems, not into a demo UI. Visible costs Model and compute costs are part of the plan. No team replacement People stay in charge of decisions - see the AI FAQ. Example setup (illustrative) A nightly job reconciles shop stock with the ERP; a daytime pipeline classifies support e-mails and files drafts in Bitrix24. Goal: less copy-paste, traceable errors. [Python](https://webdoka.com/python/) [FastAPI](https://webdoka.com/fastapi/) [Bitrix24](https://webdoka.com/bitrix24/) Jobs Frequently asked questions Between a script and a platform. Why not PHP? Often it works. Python sits better with data, AI and mixed libraries. The domain logic can stay in Symfony. Jupyter in production? No. Notebooks for understanding, jobs for running. Do we need data scientists? For many automations and RAG pilots: no. For your own models: sometimes. We tell you when. GDPR? Data classes and storage locations before the pilot. Details on the AI page. Packages, venv, Docker? Yes - reproducible. No “works on my machine”. How do we start? One job or one RAG slice. A fixed scope after a call. More stacks Related technologies we often use alongside. [FastAPI](https://webdoka.com/fastapi/) [AI adoption](https://webdoka.com/ai/) [Bitrix24](https://webdoka.com/bitrix24/) [Web development](https://webdoka.com/web-development/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) Python that runs every day? Tell us which repetitive task or which knowledge you want to offload - we propose the smallest job. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/fastapi/ # FastAPI - APIs with bite. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ FastAPI APIs & AI - FastAPI FastAPI - APIs with bite. Lean, typed APIs for integrations and AI orchestration. OpenAPI included - without a framework cathedral. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) OpenAPI Orchestration RAG Webhooks When FastAPI fits When you need a clear HTTP edge - in front of models, jobs or several clients. AI without a door A model in a notebook, no auth, no limits. FastAPI becomes the door. Many clients Shop, CRM, internal tool. One contract, versioning, error codes. Webhooks & events Clean up incoming events, sign them, pass them on. PHP stays the core You do not want to migrate - just a fast edge in front of it or beside it. What we deliver in FastAPI Contract, security, operations. APIs Pydantic models, OpenAPI, auth (token/OIDC), validation. AI orchestration RAG pipelines, prompt routing, fallbacks. See AI adoption. Jobs behind the API Long-running work in queues, status endpoints, webhooks back. Integration Bitrix24, Shopware, Symfony/Laravel - as clients, not as copies. Approach: contract first Before we wire up models, the API contract is in place. Clients should build against a schema, not against our mood. - Define resources and auth - OpenAPI as the source, not as an afterthought - Pilot with limits, logs and a cost cap - Handover: spec, runbook, staging Typical environment FastAPI, Python 3, Uvicorn/Gunicorn, often Redis or a queue. Models via API. PHP systems remain the system of record. [Python](https://webdoka.com/python/) [AI](https://webdoka.com/ai/) [Bitrix24](https://webdoka.com/bitrix24/) [Node.js](https://webdoka.com/nodejs/) How a FastAPI edge takes shape Spec, slice, hardening. 1 Contract Endpoints, errors, auth. In writing. 2 Slice One flow in staging against real data. 3 Harden Rate limits, timeouts, observability, PII. 4 Operate Deploy, metrics, optional maintenance. What integrations rely on APIs you can quote. OpenAPI taken seriously The spec does not lie. Breaking changes are real work, not just “some Wednesday”. AI with brakes Costs, timeouts, human in the loop - part of the design. No shadow platform FastAPI orchestrates, it does not replace your CRM. Example setup (illustrative) Internal assistant: FastAPI orchestrates RAG across the manual and the ticket history, writes drafts into Bitrix24 and escalates when confidence is low. Target metrics: first response, sources, cost per request. [FastAPI](https://webdoka.com/fastapi/) [Python](https://webdoka.com/python/) [AI](https://webdoka.com/ai/) [Bitrix24](https://webdoka.com/bitrix24/) Frequently asked questions API questions, briefly. FastAPI or Node.js? Close to Python and AI: FastAPI. A JS team and a BFF in front of an SPA: often Node.js. Sometimes both, clearly separated. Django or Flask? Django when the admin or CMS lives in Python. We know Flask. For APIs plus AI, FastAPI is usually the shorter route. Self-hosted LLM? When data protection or costs call for it. Otherwise API models plus RAG. How do you version? URL or header, with visible deprecation. Clients get advance notice. Auth? Token, OIDC or m2m - depending on the client. No open endpoints “because it is internal”. How do we start? One contract plus one flow. A fixed scope after the kickoff. More stacks Related technologies we often use alongside. [Python](https://webdoka.com/python/) [AI adoption](https://webdoka.com/ai/) [Node.js](https://webdoka.com/nodejs/) [Bitrix24](https://webdoka.com/bitrix24/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) An API with a contract? Tell us the clients and the first flow - we outline the spec and the pilot. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/wordpress/ # WordPress that stays stable. [Home](https://webdoka.com/)/ [Technologies](https://webdoka.com/technologies/)/ WordPress CMS - WordPress WordPress that stays stable. Content sites and editorial hubs - updates, performance and an admin area the editorial team actually uses. No theme zoo. [Start a project](https://webdoka.com/contact/) [All technologies](https://webdoka.com/technologies/) Content Editorial Landings Woo-light When WordPress is enough - and when it is not Plenty of content, clear templates. Little business logic. As soon as processes get demanding, we talk about Laravel or Shopware. Editors left waiting Pages only the agency is allowed to touch. We build blocks that editors understand. Plugin sprawl A security risk and slow page loads. We throw out whatever has no owner. Marketing landings Campaign pages with tracking, forms and several languages - without a new theme every time. Shop attempts WooCommerce for small catalogues. Once catalogue and ERP demands grow: Shopware. We name the cut-off. What we deliver in WordPress Hardened, lean, updatable. Sites & hubs Topics, blocks, several languages. Gutenberg where it helps. Forms & CRM Leads into Bitrix24 or e-mail - with spam protection and logging. Hardening Updates, backups, staging, firewall basics, performance. Integration Headless only when the channels justify it. Otherwise classic and fast. Approach: a CMS stays a CMS WordPress is not an application server. We hold that line - and move business logic into Laravel or Symfony once it appears. - Content and templates before plugins - Update and backup path on day one - Only plugins with an owner and a fallback plan - Handover including short editorial training Typical environment Current WordPress, a custom theme or a lean block theme. Often Shopware or a PHP backend alongside it. [Shopware](https://webdoka.com/shopware/) [Laravel](https://webdoka.com/laravel/) [Bitrix24](https://webdoka.com/bitrix24/) Staging How we deliver WordPress Content first, gimmicks last. 1 Content Types, navigation, who maintains what. 2 Build Theme and blocks, forms, tracking. 3 Harden Staging, updates, speed, backup. 4 Hand over Training, runbook, optional maintenance. What editorial teams rely on No surprises after the relaunch. Updatable We build so that core updates are nothing to fear. Honest about shops Woo only when small. Otherwise the e-commerce cluster. Ongoing care Security and content help through support. Example setup (illustrative) Corporate hub: news, careers, campaign landings. Lean theme, forms into Bitrix24, staging for the editorial team. Goal: editors publish on their own, fewer agency tickets. [WordPress](https://webdoka.com/wordpress/) [Bitrix24](https://webdoka.com/bitrix24/) Blocks Staging Frequently asked questions CMS questions without plugin advertising. Is WordPress insecure? Unhardened plugins are insecure. A hardened WordPress with staging and updates is fit for daily use. Headless? Only with several channels and a budget for two systems. Otherwise classic. Multilingual? Yes, with one concept - not three plugin variants in parallel. WooCommerce? For small catalogues. From B2B or ERP onwards: Shopware. Do you take over existing sites? Yes. Clean-up first, features after. How do we start? A relaunch outline or a hardening package. Get in touch. More stacks Related technologies we often use alongside. [Shopware](https://webdoka.com/shopware/) [E-commerce](https://webdoka.com/ecommerce/) [Maintenance](https://webdoka.com/maintenance/) [Bitrix24](https://webdoka.com/bitrix24/) [All technologies](https://webdoka.com/technologies/) [Services](https://webdoka.com/services/) Content that keeps running? The number of pages and who works on content - that is enough for a proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/cases/ # Projects with substance. [Home](https://webdoka.com/)/Cases Cases · Case studies Projects with substance. Here we publish approved cases - with real numbers and a clear scope. Currently: Webdoka.net (SEO SaaS on Laravel), New Tab from Webdoka (Chrome and Firefox extension), and Resume PDF for hh.ru (Chrome extension for bulk resume download). View the cases [Start a project](https://webdoka.com/contact/) [Laravel](https://webdoka.com/laravel/) SEO SaaS Chrome · Firefox TypeScript Case · SaaS · Extension Approved case studies A short overview - open the full case study with one click. /cases/webdoka-net/ SaaS · Laravel · AI [Webdoka.net - SEO SaaS platform](https://webdoka.com/cases/webdoka-net/) Multi-tenant SaaS for SEO: semantics, SERP clustering, rank monitoring, site audits, credit billing and AI adoption plans. Operated and developed further since 2021. 2026Year since 2021Support 163CRM tasks 1,018 hEffort [Read the case study](https://webdoka.com/cases/webdoka-net/) [Start a project](https://webdoka.com/contact/) /cases/new-tab/ Extension · Chrome · Firefox [New Tab from Webdoka](https://webdoka.com/cases/new-tab/) Browser extension that replaces the default new tab with a working start page: visual bookmarks, folders, notes, time and weather widgets. Local-first data, UI in 50+ languages. 2026Year Chrome + FFStores 50+Languages MV3Manifest [Read the case study](https://webdoka.com/cases/new-tab/) [Start a project](https://webdoka.com/contact/) /cases/hh-resume-pdf/ Extension · Chrome · HR [Resume PDF for hh.ru](https://webdoka.com/cases/hh-resume-pdf/) Chrome extension for hh.ru employer response pages: bulk-download candidate resumes as PDF. Up to 100 files per run, filenames by surname, data stays in the browser. 2026Year up to 100PDFs MV3Manifest EN + RUUI [Read the case study](https://webdoka.com/cases/hh-resume-pdf/) [Start a project](https://webdoka.com/contact/) Ready for your next release? Tell us briefly what you need - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/cases/new-tab/ # New Tab from Webdoka [Home](https://webdoka.com/)/ [Cases](https://webdoka.com/cases/)/ New Tab Case study · Extension · Chrome & Firefox New Tab from Webdoka Browser extension for Chrome and Firefox that replaces the default new tab with a working start page: visual bookmarks, folders, notes, time and weather widgets, custom background. Data stays local; UI in 50+ languages. [Chrome Web Store](https://chromewebstore.google.com/detail/new-tab-from-webdoka/jjjdedmaiehjfdokniaggdikpbljmalc) [Firefox Add-ons](https://addons.mozilla.org/en-US/firefox/addon/new-tab-webdoka/) [Start a project](https://webdoka.com/contact/) See the task Year 2026 [Chrome Extension](https://chromewebstore.google.com/detail/new-tab-from-webdoka/jjjdedmaiehjfdokniaggdikpbljmalc) [Firefox](https://addons.mozilla.org/en-US/firefox/addon/new-tab-webdoka/) TypeScript Vite MV3 2026 Year of the current release Chrome + Firefox Published in both stores 50+ languages UI via extension locales MV3 Manifest V3 architecture Local-first Bookmarks stay on device Challenge The task Turn an empty new tab into a daily start page - without sending bookmark data to the cloud. Starting point The standard new tab is empty and useless for people who juggle many sites, keep projects in folders, leave notes on cards, pick a custom background and choose a UI language without changing the browser language. The goal was a product-grade NTP for Chrome and Firefox: visual cards with previews, folders and subfolders, notes, quick save, widgets and store publication - with data staying local. Core complexity Several product requirements had to land in one extension: - Own NTP for Chrome and Firefox - Visual cards with previews - Folders and subfolders - Notes on folders and cards - Quick save via menu, hotkeys and popup - Time and weather widgets - Local storage and 50+ languages - Publish to Chrome Web Store and Firefox Add-ons Solution What we built A local-first new-tab product for Chrome and Firefox - shipped to both stores. Product approach New Tab from Webdoka is a product by the Webdoka team. It replaces the default new tab with a working start page: visual bookmarks, folders, notes, widgets and a custom background. Architecture: service worker, content script, newtab page and popup. Storage is local; IndexedDB holds previews. Weather comes from Open-Meteo with a local cache. Backgrounds are served from the Webdoka CDN. Delivery and stores Built with Vite 6 and TypeScript on a vanilla DOM stack (no React). Product site: [newtab.webdoka.com](https://newtab.webdoka.com). Live in [Chrome Web Store](https://chromewebstore.google.com/detail/new-tab-from-webdoka/jjjdedmaiehjfdokniaggdikpbljmalc) (id jjjdedmaiehjfdokniaggdikpbljmalc) and [Firefox Add-ons](https://addons.mozilla.org/en-US/firefox/addon/new-tab-webdoka/) (new-tab-webdoka). Scope of delivery From NTP UX to store publication - what was actually delivered. - Product concept and NTP UX - Chrome MV3 and Firefox extensions - Visual bookmarks, folders and notes - Context menu and hotkeys - Time and weather widgets - Background catalog and Preferences Lab - 50+ locales and store publication Features What the extension does From visual bookmarks to store publishing - the product surface in five blocks. Visual bookmarks Cards with previews, folders and an Unsorted inbox. Drag-and-drop keeps projects tidy; open all links in a folder at once, or copy links for chats without leaving the start page. The NTP becomes a visual workspace instead of a blank browser surface - sites and projects stay one click away. Previews Folders Unsorted Drag-and-drop Notes on folders and cards Brief or template notes on folders, plus per-site notes on cards. Copy to clipboard when you need the text in a ticket, chat or draft. Context stays next to the bookmark - not in a separate notes app that you open after the page load. Folder notes Card notes Clipboard Save pages Context menu, hotkeys and popup: Alt+S saves a selected area, Shift+Alt+S sends the page to Unsorted. Custom preview when the default capture is not enough. Capture fits the browsing flow - no separate add-bookmark ritual for every tab you want to keep. Context menu Hotkeys Popup Custom preview Widgets, background, settings Multi-city time, a 7-day weather cache via Open-Meteo, background presets, Preferences Lab and HTML bookmark import for people who already have a library. The start page feels personal without a cloud account for bookmarks - settings stay on the device. Time Weather Backgrounds Preferences Lab Localization and publishing UI in 50+ languages via _locales. Landing on [newtab.webdoka.com](https://newtab.webdoka.com), listing in Chrome Web Store and Firefox Add-ons. The product is not only an internal demo - it is a published extension with a public site and store pages. 50+ locales Landing CWS Firefox Add-ons How it looks Extracts from the extension UI - overview, folders, notes, preferences. New Tab overview - the working start page after install. Folders and cards - projects grouped with previews. Notes and widgets - context next to the bookmarks. Save pages - menu, hotkeys and popup into Unsorted. Preferences and backgrounds - presets and Preferences Lab. Technology Tech stack TypeScript and Vite 6 - MV3 extensions with local storage and IndexedDB. TypeScript Typed UI and extension logic across newtab, popup, content script and service worker. Vite 6 Build pipeline for the extension packages - fast iteration without a React runtime. Chrome MV3 / Firefox Manifest V3 for Chromium and a matching Firefox add-on, published to both stores. IndexedDB + local storage Previews in IndexedDB; bookmark structure and settings in local storage - no cloud account required. TypeScript Vite 6 MV3 Firefox IndexedDB Local-first Results Outcome - shipped Product live in both stores - local-first privacy and a multilingual NTP. 2 stores Chrome Web Store and Firefox Add-ons Local-first No cloud account for bookmarks 50+ UI languages MV3 Modern extension architecture 2026 Current product year Result for the product A working NTP with visual bookmarks, folders, notes and widgets. Privacy stays local-first: no cloud account is required to keep the bookmark library. The UI ships in 50+ languages, and the extension is live in both major stores. For Webdoka The case shows product delivery beyond client sites: a public extension, a landing on [newtab.webdoka.com](https://newtab.webdoka.com) and store publication for Chrome and Firefox. [Request a similar project](https://webdoka.com/contact/) [All cases](https://webdoka.com/cases/) Ready for your next release? Tell us briefly what you need - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/cases/hh-resume-pdf/ # Resumes to PDF for hh.ru [Home](https://webdoka.com/)/ [Cases](https://webdoka.com/cases/)/ Resume PDF Case study · Extension · Chrome · HR Resumes to PDF for hh.ru Chrome extension for hh.ru employer response pages: bulk-download candidate resumes as PDF without manual saves. Up to 100 files per run, filenames by surname, data stays in your browser. [Chrome Web Store](https://chromewebstore.google.com/detail/hbibomlggacmlfgodeeibhpdoalpfgpm) [Product site](https://hh.webdoka.com/) [Start a project](https://webdoka.com/contact/) See the task Year 2026 [Chrome Extension](https://chromewebstore.google.com/detail/hbibomlggacmlfgodeeibhpdoalpfgpm) MV3 EN + RU v1.3 2026 Year of the current release Up to 100 PDF files per run MV3 Manifest V3 architecture EN + RU UI via chrome.i18n Browser-local No resume data on our servers Challenge The task Save dozens of hh.ru resumes as PDF for offline review - without clicking each candidate one by one. Starting point Recruiters and HR teams on hh.ru open employer response pages with tens or hundreds of applicants. Each resume must be saved manually - slow, error-prone file names, no batch export from hh.ru itself. The goal was a focused Chrome tool for employer response pages only: one action to download many PDFs, readable filenames, progress in the popup, and no cloud upload of candidate data. Core requirements The extension had to stay narrow and trustworthy: - Works on hh.ru employer response pages only - Bulk or selected download, up to 100 PDFs per run - Filenames by candidate surname - Processing and downloads stay in the browser - Chrome MV3, EN and RU UI, Chrome Web Store release Solution What we built Resume PDF - a Chrome extension by Webdoka for hh.ru recruiting workflows. Product approach Resume PDF (Резюме в PDF) adds a popup and content scripts on hh.ru employer response pages. The extension collects resume links on the page, fetches PDFs through Chrome APIs and saves them via chrome.downloads - with a stepper for batch size and live progress. Built with vanilla JavaScript on Manifest V3: service worker, content scripts and popup. UI strings in English and Russian through chrome.i18n. Current release around v1.3.0. Delivery and site Product landing: [hh.webdoka.com](https://hh.webdoka.com/) with welcome and privacy pages. Listed in [Chrome Web Store](https://chromewebstore.google.com/detail/hbibomlggacmlfgodeeibhpdoalpfgpm). Help: [welcome guide](https://hh.webdoka.com/welcome/), [privacy policy](https://hh.webdoka.com/privacy/). Chrome only - no Firefox or Edge builds in this release. Scope of delivery From popup UX to store publication - what was actually delivered. - Product concept and popup UX - Chrome MV3 extension (vanilla JS) - Bulk and selective PDF download - Filename rules by surname and resume id - Progress, statuses and error handling in popup - EN and RU localization - Landing, welcome, privacy and Chrome Web Store listing Features What the extension does Bulk PDF export tuned for hh.ru employer workflows - three core blocks. Every resume, one button Open a vacancy's applicants on hh.ru and download every candidate as PDF in a single click. Need fewer files? Set a number in the stepper (up to 100) and download only that batch. Up to 100 PDFs Stepper One click Downloads run in the background Close the popup - files keep saving. Progress stays visible in the extension UI while Chrome works through the queue with pauses so hh.ru is not overloaded. Background queue Progress Closeable popup Files named by surname Each PDF is saved as Surname Name_.pdf when the name is available, otherwise resume_.pdf - straight into Downloads, without manual renaming. By surname Downloads folder Local-first Workflow Three steps From install to a folder of PDFs on the employer response page. 1. Install and open responses Install from Chrome Web Store, sign in to hh.ru as an employer and open a vacancy response list. 2. Set batch size Open the extension popup, pick how many resumes to save (up to 100) and start the run. 3. Collect PDFs Chrome saves files to your download folder with readable names. Repeat on the next page if needed. Disclaimer Resume PDF is not an official hh.ru product and is not affiliated with HeadHunter. The extension works only on employer response pages where you already have access through your hh.ru account. It does not bypass hh.ru permissions or store resumes in the cloud. For Webdoka The case shows a narrow HR utility shipped as a public Chrome extension: MV3 architecture, localized popup, product site and store listing - similar to how we deliver client-facing tools. [Request a similar project](https://webdoka.com/contact/) [All cases](https://webdoka.com/cases/) Need a Chrome tool like this? Tell us briefly what you need - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/cases/webdoka-net/ # Webdoka.net [Home](https://webdoka.com/)/ [Cases](https://webdoka.com/cases/)/ Webdoka.net Case study · SaaS · SEO Webdoka.net A SaaS platform for SEO: semantics, SERP clustering, rank monitoring, site audits, credit billing and AI adoption plans - multi-tenant, asynchronous, production-ready. [Start a project](https://webdoka.com/contact/) See the task Year 2026 [Laravel](https://webdoka.com/laravel/) since 2021 163 CRM tasks 1,018 h [AI](https://webdoka.com/ai/) 2026 Year of the current build stage Laravel Platform and backend API since 2021 Continuous product development 163 Tasks in the CRM 1,018 h documented effort Challenge The task Not just a UI refresh - a new product in place of the old SEO semantics service. Starting point The existing service for SEO semantics covered only part of the picture. What was needed was a full multi-tenant SaaS: organisations, projects, roles, wallet, paid actions and an architecture that can take on new modules without a rebuild every time. The goal was a dashboard in which teams handle the full cycle - from keyword collection to the adoption plan after the audit - with transparent costs and traceable background jobs. Core complexity Several heavy SEO processes had to come together in one product: - Collecting and filtering semantics - Analysis of search results (SERP) - Building the semantic core - Daily rank monitoring - Technical and marketing-side audits - Content changes and their impact on positions - Integrations and control of costs and balance Solution What we built A production SEO SaaS with a dashboard, team work, credit billing, queues and AI. Product approach The platform helps to collect a semantic core, cluster queries by SERP, track positions, keep control of changes on the site, start audits and receive an adoption plan with ready-made commands for the AI code editor. Multi-tenant: every user works inside an organisation, creates projects, connects integrations and starts SEO operations from a single dashboard. Heavy jobs run asynchronously through the queue - status, reports, tables and export stay visible. Credit model Before a run starts, the system estimates the cost, reserves the amount on the organisation balance and charges the actual value on completion - or releases the remainder. That keeps the platform protected against unpaid heavy jobs, and spending stays traceable for the client. The result: an in-house SEO SaaS for the full project cycle - as a standalone product and as an agency tool for audits, support and improvements on client sites. Scope of delivery From product architecture to operations - what was actually delivered. - Product architecture and an extensible domain model - Backend API and personal dashboard - Organisations, projects, roles and team work - Credit billing with reserve, settlement and history - Background queues for heavy SEO jobs - Integrations, SEO audits and AI modules - Deployment, monitoring and ongoing support Features Modules in the dashboard The cycle from semantics to adoption plan - in one product. Semantics Users collect key phrases, pull frequencies from Wordstat, filter irrelevant queries with AI and cluster the SERP by URL overlap. The outcome is an AI semantic core with keywords mapped to pages of the site. Filters, clusters and the core stay in the project context - exportable and wired into the audits and monitoring that follow. Wordstat AI filter SERP clustering Monitoring The platform records positions in Yandex, Google and Bing, tracks changes to title, meta, H1 and page content, evaluates organic traffic from connected sources and checks page speed via PageSpeed Insights. Teams see not only ranking movements, but also which on-page changes come with them - without clicking separate tools together. Google Yandex Bing PageSpeed Audits & delivery Technical and full SEO audits including crawl and PageSpeed metrics; they feed into AI reports. After the audit comes an adoption plan: steps, done criteria and commands for the AI code editor. The path from diagnosis to delivery stays in the same dashboard - fewer breaks between audit PDF and ticket backlog. Crawl AI report Adoption plan Integrations Yandex.Metrica, Google Search Console and Yandex.Webmaster can be connected per project. Tokens are stored encrypted and used only in the project context of the client. These connections feed monitoring and audits - without making credentials visible outside the respective tenant. Search Console Metrica Webmaster Billing & administration Organisation balance, transaction history, promo codes, trial credits, low-balance notices, BYOK keys for external APIs and an admin area for users, credits, plans and AI cost statistics. Heavy actions stay tied to the credit model: estimate, reserve, actual settlement - transparent for the client, protected for the platform. Credits Promo BYOK Admin How it looks Extracts from the dashboard - semantics, monitoring, audits and integrations. Dashboard overview - projects, jobs and the entry point to the SEO modules. Semantics: collection, filters and clustering. Monitoring: positions and on-page changes. Audits: reports and adoption plan. Integrations: Search Console, Metrica, Webmaster. Technology Tech stack Laravel as the backbone - queues, API, multi-tenant and AI connectivity. Laravel platform Backend API, domain services, auth and multi-tenant isolation across organisations and projects. Queues & jobs Heavy SEO runs asynchronously: crawl, clustering, rank checks, audits - with visible status and reports. AI modules Filtering of irrelevant queries, AI semantic core, audit reports and adoption plans including editor commands. Integrations Search Console, Metrica, Webmaster, Wordstat, PageSpeed - tokens encrypted and bound to a project. Billing Credit wallet, reserve and settlement, promo, trial, BYOK and admin for plans as well as AI costs. Operations Deployment, support and further development since 2021 - the product is still actively growing (year 2026). [Laravel](https://webdoka.com/laravel/) [AI adoption](https://webdoka.com/ai/) Queues Multi-tenant API Credit billing Results Numbers - honestly Approved metrics from the CRM and time tracking - as on the source case page. 163 Tasks in the CRM 1,018 h documented effort since 2021 continuous support 2026 current build stage Laravel product platform Result for the product An SEO SaaS that covers the full cycle: semantics and audit, monitoring, change analysis and adoption plan. Ready to use as a standalone product and as an agency tool for audits, support and delivery on client sites. For Webdoka The case strengthens several clusters at once: web development, operations, [AI adoption](https://webdoka.com/ai/), SEO audit and ongoing support - built on [Laravel](https://webdoka.com/laravel/). [Request a similar project](https://webdoka.com/contact/) [All cases](https://webdoka.com/cases/) Build something similar? Tell us briefly what you need - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/about/ # Team behind stable releases. [Home](https://webdoka.com/)/About us About us Team behind stable releases. Webdoka builds and runs web systems for mid-sized companies in Europe and beyond - with short decision paths, clear communication and a focus on systems that hold up in daily use. [Start a project](https://webdoka.com/contact/) [Services](https://webdoka.com/services/) The agency Webdoka is a lean web agency built around owner Dobrusin Jurij. The base is Tbilisi - daily work runs in English with clients in Europe and beyond: mid-sized companies, retailers, in-house IT. Clear briefings, traceable releases, people you can reach. We combine product thinking with craft: architecture that teams can actually operate, code without showmanship, and support that does not stop after go-live. On top of that come automations and AI building blocks - Python, FastAPI, RAG - always connected to existing shops, portals and CRM systems. - Coordination in English or German - without translation friction - Owner-level delivery instead of anonymous ticket handling - Development and operations from one team Stacks we know well We choose technology by goal and team - not by trend. [Symfony](https://webdoka.com/symfony/) [Laravel](https://webdoka.com/laravel/) [Shopware](https://webdoka.com/shopware/) [Vue](https://webdoka.com/vue/) [Angular](https://webdoka.com/angular/) [Node.js](https://webdoka.com/nodejs/) [WordPress](https://webdoka.com/wordpress/) [Bitrix](https://webdoka.com/bitrix/) [Python](https://webdoka.com/python/) [FastAPI](https://webdoka.com/fastapi/) [AI](https://webdoka.com/ai/) [Yii](https://webdoka.com/yii/) [Cloud](https://webdoka.com/cloud-outstaffing/) [All stacks](https://webdoka.com/technologies/) What guides us The values we measure projects and releases against - AI work included. Stable systems Maintainable architecture, tests and CI - so growth does not reinvent the foundation every time. Support that lasts Availability, clear SLAs and runbooks. Incidents are part of the job - not a surprise. Craft instead of show Clean modules, honest scope conversations, documentation and handover as standard - not as an upsell. Built for mid-sized teams No bloated enterprise overhead. Short paths to Jurij and the delivery team - decisions without a 12-person committee. AI with real integration Assistants and automations sit inside your processes - CRM, docs, shop - not as an isolated demo. [AI adoption](https://webdoka.com/ai/). Building trust What clients can rely on when they work with Webdoka. A direct contact person Dobrusin Jurij stays in the loop - from the first request to day-to-day operations. No handing you off into nowhere. Scope in writing Goals, risks and deliverables before the first sprint - traceable and without empty buzzwords. Handover included Docs, deployment path and knowledge transfer are part of the job. Optional: maintenance or outstaffing afterwards. Location & availability Tbilisi - remote-first for clients in Europe and beyond. Phone: [+49 176 57730327](tel:+4917657730327) Email: [sales@webdoka.de](mailto:sales@webdoka.de) Is Webdoka a good fit for you? If you need stable releases, honest assessments and someone who is still reachable after launch - write to us. [Go to contact](https://webdoka.com/contact/) [View cases](https://webdoka.com/cases/) Ready for your next release? Describe briefly what you need - we come back with a concrete proposal. [Start a project](https://webdoka.com/contact/) [Call us](tel:+4917657730327) --- ## https://webdoka.com/contact/ # Write to us - directly. [Home](https://webdoka.com/)/Contact Contact Write to us - directly. Describe briefly what you need - stack, goal, timeframe. We come back with a concrete next step. Go to the form [Call us](tel:+4917657730327) Start a project . For genuine enquiries: sales@webdoka.de Website Name Email Company Topic Web development E-Commerce Maintenance & support Cloud & outstaffing AI adoption Technologies / stack Python / FastAPI Something else Message Start a project By submitting the form you agree to the processing of your data in line with our [Privacy policy](https://webdoka.com/privacy/). We usually reply within one business day. Thank you! We will be in touch shortly. Reach us directly Phone [+49 176 57730327](tel:+4917657730327) Email [sales@webdoka.de](mailto:sales@webdoka.de) Contact person Dobrusin Jurij Location / address Tbilisi, Georgia Remote-first, clients in Europe and beyond Response time: usually within one business day. For urgent incidents please call us on [+49 176 57730327](tel:+4917657730327). What happens next No opaque process - three clear steps. 01 - Request Form, email to sales@webdoka.de or a call. Short enough for us to size the scope. 02 - Scoping A short call with Dobrusin Jurij: goals, risks, stack and a realistic timeframe. 03 - Proposal A concrete next step - discovery, fixed-price package or ongoing support - in writing and easy to follow. Direct contacts +49 176 57730327 · sales@webdoka.de · Tbilisi · Contact person: Dobrusin Jurij Stack still open? No problem. Under [Technologies](https://webdoka.com/technologies/) you will find twelve stack pages - or leave the topic open and we give you an honest recommendation. Ready for your next release? Describe briefly what you need - we come back with a concrete proposal. Go to the form [Call us](tel:+4917657730327) ---