Forint Alkotás
ContactBook a call
Technology

One platform, no plugins. This is how Neuramerce is built.

Everything a store needs is a module of the same system, on the same database, built by the same team. This is the map.

CHANNELSStorefrontper language, own domainB2B portalcustomer prices, on accountMarketplacesBol, Amazon, Google ShoppingE-mail and campaignsautomations, Meta, GoogleNEURAMERCECatalogueattributes, filters, bundles, EANOrders and customersstatuses, returns, B2BInventorylocations, purchasing, suppliersContent and SEOpages, blog, meta, rank trackingTranslationsper language, with stale statusMedia and 3Dfrom CAD to web and AROne database per workspacePostgreSQL, separate schema per client, daily backupIntegrations layerall external systems through one managed point, never per moduleAGENTSAI agents with access to the platformorders, stock, translations, customer questions; every action logged and traceableEXTERNAL, VIA THE INTEGRATIONS LAYERPaymentMollie, cards, local methodsShipping and fulfilmentcarriers, external warehouseAccountinginvoices and paymentsExisting shopWooCommerce during migrationMEASURINGError monitoringevery error with contextSpeedCore Web Vitals per pagePositionsreal SERP, per target URL
Principles

Four choices that decide everything.

One database per client

Every workspace has its own schema. No shared tables between clients, no filter that can be forgotten.

Integrations in one place

An external system is connected once, managed centrally. Modules talk to that layer, never directly to an API.

Translation is a status

A changed source text marks every translation as stale. The admin shows what is left, the storefront never silently shows the old text.

Agents are traceable

An agent acts within the same rights as an employee, and every action is in the log with the reason attached.

In names and numbers

What runs underneath.

For those who want to know. For those who do not: it works, and it is ours.

ApplicationNext.js, TypeScript, server-side rendered for speed and visibility
DatabasePostgreSQL, one schema per workspace, daily backup off the server
HostingRailway, European data centres; media on Cloudflare, mail on our own servers at Hetzner
StorefrontStatic where possible, dynamic where needed; CDN cache with targeted invalidation
3D and ARModels generated from CAD or eDrawings files, optimised for mobile
SecuritySessions via signed tokens, rights per role, external keys server-side only
MonitoringHealth checks and error tracking on every deploy; we hear about a problem before you report it