Part 1: Website Builders for Russia and International Markets
Tilda
What it is: a website builder with a visual editor and Zero Block for custom layouts.
Where it works: Russia and international markets.
Integrations:
- CRM: 20+ data-collection services; leads can be sent to email, Google Sheets, or CRM.
- Payments: Stripe, PayPal, 2Checkout.
- Analytics: built-in statistics, Google Analytics, Tilda Webmaster.
- Communications: JivoSite, Chatra, callback services.
- Custom code: HTML, JS, CSS embedding.
- API: static HTML export and API integrations.
Microservices: Tilda does not provide a microservice architecture. You work inside the platform and can only connect external services through code or supported integrations.
Best for: landing pages, promo sites, and fast launches.
Shopify
What it is: an ecommerce platform with ready-made commerce infrastructure.
Where it works: international markets. Registration for Russian legal entities and individuals is closed.
Integrations:
- Sales channels: Facebook, Instagram, TikTok, Google, Pinterest, Snapchat.
- Logistics: Flexport, ShipBob, Shipfusion, ShipMonk.
- Marketing: email and SMS campaigns, influencer workflows.
- API: GraphQL Admin API for custom extensions.
Microservices: Shopify allows custom applications and integrations through APIs, but the core architecture remains closed. You extend the Shopify ecosystem rather than build your own platform core.
Best for: international D2C brands and stores focused on sales.
Part 2: Russian Alternatives
Yandex KIT
What it is: a free platform for online stores and a Russian alternative for a fast ecommerce launch.
Where it works: Russia.
Integrations:
- Marketplaces: Wildberries, Ozon, Yandex Market.
- Warehouse systems: 1C, MoySklad.
- Product import: Excel and YML feeds.
- Payments: Yandex Pay, Split, CloudPayments.
- Delivery: Yandex Delivery, CDEK, Ozon, Russian Post.
- Promotion: Yandex Direct and Metrica.
Microservices: no. It is a ready-made platform with predefined architecture rather than a base for building your own service landscape.
Best for: a quick ecommerce start in Russia.
1C-Bitrix
What it is: a commercial CMS and ecommerce platform widely used in Russia, especially where 1C integration is important.
Where it works: primarily Russia and CIS markets.
Integrations:
- 1C: deep exchange with products, prices, stock, orders, and related data.
- CRM: close integration with Bitrix24.
- REST API: for custom applications and integrations.
- Application marketplace: ready-made partner solutions.
Microservices: limited. REST APIs make integration possible, but the platform core is closed.
Best for: companies where 1C integration and enterprise-style Russian infrastructure are critical.
OpenCart
What it is: an open-source ecommerce solution.
Where it works: Russia and international markets.
Integrations:
- 1C: exchange modules.
- MoySklad: integrations through plugins.
- Payments: Robokassa and other gateways.
Microservices: possible. Open source gives developers freedom to build custom integrations and services.
Best for: teams that want control without recurring platform license fees.
Other Russian Platforms
- Craftum: built-in AI tools and catalogs up to tens of thousands of products.
- Bazium: Telegram integration for incoming requests.
- Nethouse: business-oriented plans and templates.
- AdvantShop, UMI, Diafan, InSales, CS-Cart — additional options depending on catalog size, integrations, and ownership requirements.
Part 3: WordPress — Works in Both Worlds
What it is: an open-source CMS. You own the files, database, and code.
Where it works: anywhere — Russia, international markets, and virtually any hosting provider.
Integrations and Microservices
1C:
- EDI and exchange plugins for products, prices, stock, and orders.
- Connectors for 1C configurations and related Russian business systems.
- WooCommerce integrations for 1C exchange.
CRM:
- Contact Form 7 → Bitrix24 CRM: contacts, deals, and UTM data.
- RetailCRM: synchronization of orders, products, and stock.
- amoCRM, MoySklad, and other systems through plugins or APIs.
Delivery:
- Aggregators and carrier plugins.
- CDEK, Boxberry, Russian Post, PEC, and other services depending on the project.
Restaurants: iikoCloud integrations for WooCommerce are possible.
Microservices: WordPress can participate in a microservice architecture. You can create REST API endpoints, connect external services through webhooks, and write custom plugins for specific business logic.
Headless architecture: React or Next.js frontend + WordPress backend, REST or GraphQL depending on the task.
Asynchronous integrations: WordPress REST + external service + webhook with states such as pending/completed/failed and explicit error handling.
When These Platforms Are Not the Right Fit
When WordPress is not the best choice
No one will maintain the site. WordPress requires regular core, theme, and plugin updates. If there is no person or budget for maintenance, a managed platform may be a better fit.
The project has highly non-standard server-side logic. Complex roles, calculations, and deep internal-system integrations can exceed what WordPress should reasonably carry. Laravel, Django, dedicated services, or custom development may be more appropriate.
Security requirements are exceptional. WordPress can be secured well, but plugin quality varies. For highly regulated or critical systems, specialized enterprise platforms may be preferable.
The site is truly static. If content will not change for years, a CMS may be unnecessary; static HTML or a static-site stack can be enough.
There is no PHP expertise. Deep WordPress customization is built around PHP. Without that competence, custom work becomes dependent on external contractors.
When Tilda is not the best choice
The project must run on your own infrastructure. Tilda is SaaS. If self-hosting, independent backups, or infrastructure policies are mandatory, it is not the right fit.
Complex business logic. User roles, advanced personal accounts, and non-standard calculations quickly exceed what a page builder is designed for.
A large publishing workflow. For a content-heavy publication with frequent posts, a full CMS is usually more convenient.
A large catalog with non-standard logic. Complex variants, bundles, dynamic pricing, and specialized checkout rules can become limiting.
Infrastructure control is required. If you need your own servers, security policies, deployment rules, and complete operational control, a SaaS builder is the wrong architectural choice.
When Shopify is not the best choice
Russian business. Shopify is not a straightforward option for Russian legal entities and individuals because registration and payments are restricted.
Advanced B2B requirements. Individual terms, net payment conditions, and deeper B2B features may require Shopify Plus.
Non-standard checkout. Standard plans provide limited control over checkout logic; deeper customization may require Plus.
Complex ERP integrations. Shopify can integrate deeply through APIs, but serious ERP scenarios usually require custom development.
High API demand. API rate limits can become an architectural constraint in high-volume integrations.
App costs. Shopify may look inexpensive at the start, but recurring paid apps can accumulate significantly over time.
Summary Table
| Criterion | Tilda | Shopify | Yandex KIT | 1C-Bitrix | WordPress |
|---|---|---|---|---|---|
| Works in Russia | Yes | No / restricted | Yes | Yes | Yes |
| Site ownership | No | No | No | Partial | Yes |
| Cost model | Subscription | Subscription + apps | Low / free entry | License + development | Hosting + domain + maintenance |
| Large store | Limited | Yes | Yes | Yes | Yes |
| 1C integration | Limited | Custom | Through exchange | Built in / strong | Plugins / custom |
| Microservices | No | Limited | No | Limited | Yes |
| Custom integrations | Via code | Via API | Limited | REST API | Full freedom |
| Best for | Landing pages | International commerce | Fast start in Russia | Enterprise with 1C | Growth and control |
Main conclusion
Tilda is good for landing pages and fast launches, but it is not designed for unlimited growth.
Shopify is strong for international ecommerce, but it is a closed platform and is not a straightforward choice for Russian businesses.
Yandex KIT can be a low-friction starting point in Russia, but it is limited for complex projects.
1C-Bitrix is appropriate when 1C integration is critical, but it requires licensing and specialist support.
WordPress is for teams that want to own, control, and extend their platform. It requires more responsibility, but provides far more architectural freedom.
That is normal. A platform is a tool, and no tool is universal. The important thing is to understand where the limits of your chosen tool are and plan a transition before the business reaches those limits.
If you need a website that you control rather than a platform that controls you, the architecture should be discussed before the design begins.
