When you launch an online store, a landing page with an order form, or a SaaS service, sooner or later the same set of tasks shows up. Detect the visitor's country by IP. Convert the price to their currency. Validate the phone number on the order form. Verify a European counterparty's VAT number. Find out whether today is a working day in the destination country.
Each of these tasks looks like a small thing. But when there are ten of them, and each requires its own provider with its own API key, its own dashboard, its own invoice, and its own SLA — the picture stops being small. This is BaaS by DAPITA — a single platform that closes these recurring backend tasks behind one integration.
In this article we go through what is in the service, what problems it solves, and why it makes sense to look at infrastructure APIs as a single layer rather than a collection of separate plugins.
The problem BaaS solves
A modern online project consists of dozens of external dependencies. Advertising, analytics, payments, logistics, email — almost every block requires its own integration. Among these dependencies there is a separate category — infrastructure data. Not payments, not marketing, but small but critical functions:
- IP geolocation, to show the user the right currency and language;
- currency rates, so a USD price becomes a price in złoty or euro;
- VAT rates, to display prices with the correct tax;
- phone and email validation at form-submission time;
- timezone detection for delivery time calculations;
- IP reputation checks for proxies and bots.
Each of these can be plugged in separately. The market has dozens of niche services for each task. The problem isn't that they don't exist — it's that there are too many of them, and each one demands its own attention.
What "its own attention" means in practice:
- registration and verification of an account in every service;
- every vendor's own key format, own limits, own error responses;
- own billing — five subscriptions at €10–20 each turn into €100/month faster than you'd think;
- monitoring availability of each provider separately;
- updating documentation and SDKs whenever the API version changes;
- manual invoice reconciliation across five or six systems.
For a large business with a DevOps team this is solvable. For a small store or a startup, it's dozens of hours of routine and a permanent point of failure: if one provider raises prices or shuts down, you have to rewrite the integration.
What BaaS by DAPITA is
BaaS (Backend-as-a-Service) by DAPITA is a working service available at baas.dapita.net. It is a set of 29 public API endpoints brought together on one platform with a single authentication, a single billing system, and a single management dashboard.
The idea is simple: everything that usually gets connected separately is available behind a single API key. One account, one dashboard, one invoice, one documentation set.
What's included
Geolocation and geography
- country, region, and city detection by IP address;
- country directory with ISO codes, flags, calling codes, and currencies;
- regions and cities catalogue by country — around 3 million cities;
- postal-code lookup with two modes (within a country and globally).
Currencies
- live exchange rates for 171 currencies;
- conversion between any pair;
- historical rates for charts;
- currency directory with symbols and display formats.
Taxes and legal validation
- VAT rates for EU countries and other regions;
- VAT number validation.
Contact data
- phone number validation with country and operator detection;
- phone input masks by country;
- international phone formatting;
- email validation with domain checks.
Time and calendar
- timezone information for a specific location;
- full timezone list mapped to countries;
- holidays by country with categories (national, banking, religious);
- business-day check — is a given date a working day in a given country.
Languages
- language directory mapped to countries;
- language detection from text.
Security and analytics
- IP reputation checks (proxies, VPNs, known spam sources);
- WHOIS lookup for domains;
- DNS lookup with support for different record types;
- User-Agent parsing for browser, OS, and device detection.
Every endpoint follows the same simple pattern: an HTTP request with an API key in the header, a JSON response.
Performance
When you're running a platform that handles every visitor's request, response time becomes critical. BaaS runs on Go with PostgreSQL and Redis as the caching layer, and every endpoint is load-tested with wrk before it ships to production.
Real numbers on current hardware (4-core Intel Haswell, 8 GB RAM):
| Endpoint | Requests/sec | Latency |
|---|---|---|
| City search | 25,984 | < 5 ms |
| Phone validation | 13,270 | 8 ms |
| Phone mask | 13,190 | 8 ms |
| IP geolocation | 13,182 | 8 ms |
| Region list | 9,516 | — |
| Country directory | 8,116 | — |
| Currency conversion | 7,848 | 13 ms |
| Currency rates | 6,131 | 16 ms |
For most endpoints, latency is in the single-digit milliseconds — the user doesn't notice the API call during page load or form submission.
These numbers are headroom, not a marketing figure. Even the heaviest pricing tiers fit into a fraction of a percent of the server's peak throughput, which means: as load grows, the service won't hit the ceiling on any single endpoint.
Why it's needed: real scenarios
To stay out of the abstract, let's look at concrete situations where BaaS becomes useful.
An online store with international shipping
A buyer lands on the site. Their IP determines the country — say, Germany. The system automatically switches the interface to German, shows prices in euros (converted from the store's base currency), and adds the German VAT rate of 19%. On the checkout page, the phone field gets a German input mask. As the user types, the number is validated on the fly. The email address is checked for domain correctness. After the order is placed, the system checks whether tomorrow is a working day in Germany — if not, the order confirmation correctly states the delivery date.
All of this is six or seven calls to BaaS — instead of integrating with six or seven different services.
A B2B service with European clients
When registering a client company, the form asks for a VAT number. It is verified through the /vat/validate endpoint — the system not only confirms the number is valid but also pulls the company's registered details. Based on the country, the applicable VAT rate is determined (or reverse charge for B2B inside the EU).
A SaaS platform with abuse protection
When a new user signs up, their IP is checked through /ip/reputation. If it's flagged as a known proxy or spam source, registration requires extra verification. The User-Agent is parsed to detect suspicious clients. Email is checked against disposable-domain lists. The DNS record of the email's domain is checked for the presence of MX records.
Logistics and delivery date estimation
A store calculates the delivery date for Spain. The /business-day endpoint reports that 6 January is a non-working day (Epiphany, Reyes Magos), so the delivery is pushed by one day. The /holiday endpoint returns upcoming holidays in the recipient's country — surfaced in the manager's admin panel.
What the developer gets
From an integration standpoint, BaaS is a REST API. No SDKs to keep up to date, no proprietary protocols. Any language with an HTTP client (so, any language) talks to the service the same way.
Structurally, integration looks like this:
- Sign up at baas.dapita.net.
- Create a project and get an API key.
- Make an HTTP request with the key in the
Authorizationheader. - Receive a JSON response.
The free tier offers 5,000 requests per month with no card required — enough not just for testing, but for a full pet project or the early stage of a startup.
Tier limits are built around typical load profiles: from a personal project to a business with hundreds of thousands of requests per month. For one-off spikes, top-up packs are available without changing the plan.
The dashboard includes per-endpoint usage analytics — which methods are called the most, at what time of day, from which geography. This helps you understand how the service is actually used in your project and where you can optimize calls with caching on your side.
The documentation includes an interactive sandbox: every endpoint can be called directly from the dashboard with your API key, and you can copy a ready-made request snippet in the language you need.
Why a single platform makes sense
When infrastructure APIs are spread across different providers, several hidden costs creep into the project — costs that rarely appear on any spreadsheet.
Cognitive load. Every service is its own mental model: error format, limit semantics, billing logic. Ten services means ten models to keep in your head or in browser bookmarks.
Failure points. If one of ten providers goes down, the failure propagates through the whole chain. The more external dependencies, the higher the probability that at any given moment one of them is unavailable.
Switching cost. When a provider raises prices or changes terms, migration means rewriting code. With a single platform this problem doesn't disappear entirely, but it shrinks to a single point.
Billing and financial clarity. One invoice instead of ten makes expense tracking simpler. Especially noticeable in small businesses, where bookkeeping is often manual or semi-manual.
That said, BaaS doesn't replace specialized services where they're genuinely needed. If your project requires a full payment gateway, an enterprise-grade fraud system, or sophisticated marketing analytics — those have their own platforms. BaaS closes the layer of infrastructure data that repeats in almost every online project and that doesn't make sense to assemble piece by piece.
The bottom line
BaaS by DAPITA is a working service that brings together, in one place, the APIs that almost every project with international users will eventually need. Geolocation, currencies, taxes, contact validation, time and reputation — twenty-nine endpoints behind a single key, with throughput in the thousands of requests per second.
For the developer, that means fewer integrations and fewer docs. For the business, one invoice instead of several and predictable spend. For the project as a whole, fewer failure points and less time spent maintaining the infrastructure layer instead of building the product.
The service runs at baas.dapita.net. The free tier lets you try everything with no commitment — 5,000 requests per month, access to all 29 endpoints, no card at signup.