Brokik now runs in 25 countries — from Poland and Germany, through Norway and Spain, to Argentina, the United States, Australia, Singapore, and South Africa. Before we got to that number, we understood internationalization the way most SaaS teams do: as a file of translated interface strings. Scaling a rental management platform across that many markets taught us that assumption is wrong — and that the real difficulty sits somewhere else entirely.

Internationalization isn’t interface translation

The most common shortcut when entering a new market is: swap the strings in the interface and you’re done. That works for simple tools, but not for a product that governs the relationship between a landlord and a tenant. In rental management, the interface itself is usually the smallest part of the work. The rest is handover protocols, deposit rules, notice periods, and obligations for both parties — and those differ between countries far more than their grammar does.

That’s why internationalization at Brokik was never a localization pass bolted on at the end. It’s been part of the product spec from day one of entering each new market.

Local rental law as part of the product, not an add-on

Brokik is built for local rental law, market by market — that’s not a marketing line, it’s a description of how the team’s work actually looks for every new country. What a handover protocol must contain in Poland isn’t what it must contain in Norway or Argentina. Deposit rules, documentation of property condition, notice periods and forms — all of that differs at the level of local law, not just custom.

That distinction matters, because Brokik is a SaaS for managing rentals for landlords and tenants — not a listings marketplace. The product’s value isn’t in browsing ads; it’s in guiding both parties through a process that’s compliant with whatever law applies in their country. Lease and protocol templates are therefore part of the product core in every market, not a translation layer sitting on top of one central template. You can read more about the product itself on the Brokik page.

One domain, 25 markets — an architecture decision

It gets interesting when you compare this to another one of our products. Cheaperfordrug, our basket-based medication price comparison tool, serves 9 countries through 9 separate country domains — taniejpolek.pl, medikamentbilliger.de, cheaperfordrug.com, and so on. Brokik went the opposite direction: one domain, brokik.com, no country-specific TLDs, and still 25 markets.

Both decisions are deliberate, and both are right — for their own product. A price comparison tool is inherently local: users search in their own language for a deal in their own market, and a separate country domain helps with local trust and visibility. A rental management platform sells differently — the buying decision is about the product itself, not the local listings market, so one domain with one accumulated history of trust and links makes more sense than splitting that across 25 separate addresses. One domain also means one deployment, one piece of infrastructure, one consistent brand across every market.

That’s exactly the kind of decision that comes up on every international project: domain architecture should follow how a specific customer buys in a specific market — not a default pattern copied from a different project.

17 interface languages, one layer

Brokik’s interface is available today in 17 languages: Czech, Danish, German, English, Spanish, Estonian, Finnish, French, Croatian, Italian, Lithuanian, Latvian, Dutch, Norwegian, Polish, Slovak, and Slovenian. That’s a lot of languages, but it’s still only the layer a user sees — sitting on top of the local law and local templates described above.

The important lesson here: language coverage and legal coverage need to be tracked separately. An interface can be ready in a given language before the document templates for that specific jurisdiction are fully built out — or the other way around. Treating both as a single “market localization” task creates a false sense of readiness.

A repeatable process for entering a new market

What let us scale to 25 markets instead of getting stuck at three wasn’t a series of heroic one-off efforts for each new country. It was turning the work done for the first few markets into a checklist we repeat every time: researching local rental law and protocol requirements, localizing lease and document templates, translating the interface layer, regional configuration, and a verification pass before opening the market to users.

Every new market isn’t a project starting from zero anymore — it’s an instance of a known process, which makes entering new countries faster and less risky rather than more complicated.

AI in document adaptation and pricing

Claude runs in production inside Brokik as part of this process, supporting document adaptation and pricing for a specific market. That doesn’t mean the model is left to “figure out” local rental law from scratch on every document — the structure and rules come from templates built for that country, and AI helps apply and adapt them efficiently to a specific case. That separation of roles — AI proposes and adapts, an established structure decides — is the same approach we describe in more detail on our AI implementation page.

What this means for clients who bring us their projects

Keeping a product consistent across 25 countries, 17 interface languages, and a single domain isn’t an academic exercise — it’s a daily engineering discipline we test on our own product before we ever propose it to a client. When we talk to companies about integration, localization, or AI-assisted workflows, that same discipline — separating the visible layer from the regulatory layer, a repeatable process instead of improvising on every project — is what stands behind our work.

If you’re wondering how to pick a team for that kind of project, we wrote more about it in How to choose a partner for an AI implementation (and what to avoid). And on why it’s worth checking whether a vendor actually uses their own tools in production, see A team that runs its own AI products in production — what that changes for your business.

FAQ

Is Brokik a rental listings marketplace? No. Brokik is a SaaS for managing rentals for landlords and tenants — a tool for running the rental relationship in line with local law, not a place to browse listings.

Does each Brokik market have its own country domain? No. All 25 markets are served from one domain, brokik.com — with no country-specific endings like .pl or .de.

How many languages does the Brokik interface support? 17 languages, from Czech and Danish to Slovak and Slovenian. That’s the layer a user sees, separate from the work of building local law compliance and document templates for each market.

Does AI in Brokik interpret rental law on its own for each country? No. AI supports document adaptation and pricing based on templates built for a specific jurisdiction — it doesn’t establish the law from scratch for each case.

Does this international scaling model transfer to other industries? The principle does — separating the visible layer (language, interface) from the regulatory layer (law, processes, documents), and building a repeatable market-entry process, works anywhere a product operates across multiple jurisdictions at once.

If you’re planning a project that needs to work across more than one market — a new product or adding AI to an existing process — get in touch. We’re happy to talk through how this approach applies to your project.