Before Brokik reached 25 countries — from Poland and Germany, through Norway and Spain, to Argentina, the United States, Australia, Singapore, and South Africa — we understood internationalization the way most SaaS teams do: as a file of translated interface strings. Working across that many markets taught us that assumption is wrong.
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 spec from day one of entering each new market.
Rental law: what’s in the app, and what’s in the generator
Deposit rules, documentation of property condition, notice periods and forms differ at the level of local law, not just custom — that’s a description of the team’s work for every new country, not a marketing line. We solve this on two levels.
For all 25 markets, we’ve built lease and handover-protocol templates available in our free public lease generator, no account required. Inside the app itself — where an already-signed lease is actually run: settlements, landlord-tenant messaging, issue reports — full generation of a new lease and rental income tax calculation work for Poland today; in other markets the app exports income and cost data, and the tax filing itself stays with the landlord.
AI supports this work in daily use: it adapts an existing lease or protocol to a free-text instruction, and a setup assistant drafts property and tenant records that the user approves. The model doesn’t establish rental law from scratch — it works from the structure the team built for that market. 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. Taniej po Lek, our basket-based medication price comparison tool, serves 11 countries through 11 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. 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 makes more sense than splitting that across 25 separate addresses.
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.
A repeatable market-entry process, and 17 interface languages
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, but it’s still only the layer a user sees, sitting on top of the local law and templates described above — and language coverage needs to be tracked separately from legal coverage, since an interface can be ready in a given language before the templates for that jurisdiction are fully built out.
What let us scale to 25 markets instead of getting stuck at three was turning the work done for the first few markets into a checklist we repeat every time: researching local rental law, localizing templates, translating the interface, regional configuration, and a verification pass before opening the market. Every new market isn’t a project starting from zero anymore — it’s an instance of a known process.
We carry that same discipline — separating the visible layer from the regulatory layer, a repeatable process instead of improvising — into client projects too; we wrote about how to pick a team for that kind of work in how to choose a partner for an AI implementation, and about why it’s worth checking whether a vendor uses its own tools in a team that runs its own AI products.
In short
The biggest lesson from scaling Brokik wasn’t language — it was separating what’s shared across every market from what has to be local by definition, and building a process that repeats that split every time. If you’re planning a project that needs to run across more than one market, read more about our approach on the AI page.
Frequently asked questions
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, 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 document templates and local law work for each market.
Does AI in Brokik interpret rental law on its own for each country?
No. AI adapts an existing document to a free-text instruction 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.