All Three Trinity Guard® Data Regions Now Run on AWSOur European region moved to AWS Frankfurt. U.S. data stays in Northern Virginia.
Until October 2026, our European customers ran on a dedicated server in Budapest. That region now runs in Amazon Web Services' Frankfurt data center, so all three Trinity Guard® data regions sit on the same AWS infrastructure. Nothing changed for U.S. accounts: your patrol data stays in AWS US East, Northern Virginia.
October 2026us-east-1 · sa-east-1 · eu-central-1No action needed
Gyula GyörfiFounder of Trinity Guard® · Published October 23, 2026
Trinity Guard® data regions3 AWS regions · Europe: Frankfurt
AWS region
Active use
Moved from Budapest to Frankfurt
United States & Canada: New York, Atlanta, Miami, Orlando, Dallas, Houston, Los Angeles, San Francisco, Toronto, Vancouver
Mexico & the Caribbean: Mexico City, Monterrey, Tlalnepantla de Baz, Nassau
South America: Bogotá, Lima, Santiago, Buenos Aires
Europe: Hungary, Warsaw, Romania, Madrid
Africa & Asia: Zanzibar, Navi Mumbai
AI Summary Ready
In short: In October 2026, Trinity Guard® moved its European data region from a dedicated server in Budapest to AWS Frankfurt (eu-central-1). All three data regions now run on Amazon Web Services: Northern Virginia (us-east-1) for the United States, Canada and Mexico, São Paulo (sa-east-1) for South America, and Frankfurt (eu-central-1) for Europe. U.S. accounts were not affected, users have nothing to do, and self-hosted Enterprise deployment remains available.
Trinity Guard® has always run in three data regions: two on AWS and one on a dedicated European server in Budapest, Hungary. In October 2026, the European region moved to AWS Frankfurt. Every region now runs on the same cloud platform.
Region
AWS region code
Who it serves
Northern Virginia, USA
us-east-1
United States, Canada, Mexico
São Paulo, Brazil
sa-east-1
South America
Frankfurt, Germany
eu-central-1
Europe
Officers, managers and clients see none of this in the mobile app or the web dashboard. The change happened underneath, at the infrastructure level.
U.S. customers
What It Means for U.S. Accounts
Short answer: nothing changes, and nothing needs to be done.
U.S. patrol data stays where it was: AWS US East in Northern Virginia (us-east-1).
Officers keep the same app. Nobody has to reinstall anything.
Managers sign in to the same web dashboard with the same credentials.
Patrol history, incident reports and exports are all intact.
GPS and QR verification, Trinity Agent AI and read-only client access work exactly as before.
What does change: if your company also runs sites in Europe, or serves a client with European operations, those accounts now sit on the same AWS platform as yours.
The reason
Why We Put Every Region on One AWS Footprint
The Budapest server served us well. As the platform grew, it became more important that all three regions are built the same way.
Consistent operations. With all three regions on the same infrastructure, we update, back up and monitor them the same way. Fewer differences mean fewer chances for something to go wrong.
Scale on demand. On AWS, capacity grows with demand. When a security company with hundreds of officers signs up, no new hardware has to be bought or installed.
Availability. Each AWS region is made up of multiple, physically separate data centers, so a local failure is less likely to take the service down.
Speed. Frankfurt is one of Europe's main network hubs, so European teams in Hungary, Poland, Romania and Spain get fast response times, just as they did before.
Trinity Guard® is part of the AWS Startups program, which supports building scalable systems for the long term. We covered the region model in more detail in building a region-based global security platform.
Bottom line: the point isn't where one server sits. It's that all three regions now run as one system.
Data handling
Where the Data Lives
Every Trinity Guard® account runs in one of the three regions, and the region is chosen once, at signup. Patrol logs, checkpoints, incident reports, photos and vehicle entry and exit records are stored in that region.
For U.S. accounts, that means AWS US East in Northern Virginia. For European accounts, it now means Frankfurt, inside the European Union, so European data stays under GDPR and does not leave the EU.
Traffic between the mobile app, the web dashboard and the servers is encrypted (SSL/TLS). Card payments are handled by Stripe; Trinity Guard® does not store card data. For more on how storage location works, see our data residency guide.
Who cares
Who This Matters To
Security companies. Clients and procurement teams increasingly ask where patrol data is hosted, often as part of a vendor security questionnaire. You now have a short, verifiable answer: Amazon Web Services, U.S. East, Northern Virginia.
Property and facility clients. A plant, warehouse or logistics operator doesn't just want to know that the patrol happened. They want to know the evidence is stored somewhere reliable. Verified patrol records are only as useful as the place they're kept.
Multi-site and multinational operators. If you run sites in the U.S. and Europe, both regions now run on the same technology, and each keeps its data in its own region.
Enterprise
Self-Hosted Deployment Is Still an Option
Not every organization can use shared cloud services. For critical infrastructure or strict internal IT policies, Trinity Guard® can still be deployed on the customer's own servers or private cloud.
Note: the move to Frankfurt affects the standard cloud service only. In Enterprise deployments, data stays wherever the customer's own infrastructure is.
Run a 14-Day Guard Tour Pilot
GPS and QR patrol verification, incident reporting and read-only client access, free for 14 days with every feature included. U.S. accounts run in AWS Northern Virginia.
In the AWS US East region in Northern Virginia (us-east-1). Accounts created for the United States, Canada and Mexico run there.
Did anything change for U.S. accounts?
No. U.S. accounts were already on AWS us-east-1 and stay there. The October 2026 change moved only the European region from a dedicated server in Budapest to AWS Frankfurt.
Where does Trinity Guard® store European customer data?
Since October 2026, in the AWS Europe region in Frankfurt, Germany (eu-central-1), inside the European Union.
Do officers or managers need to do anything?
No. The app, the logins and the patrol history are unchanged. Nobody has to reinstall anything.
Were existing patrol logs and reports kept?
Yes. All historical data was moved and can still be searched and exported.
Can we run Trinity Guard® on our own servers instead?
Yes. For enterprises and critical infrastructure operators, Trinity Guard® Enterprise can run in the customer's own infrastructure or private cloud.
Same System, One Infrastructure
All three Trinity Guard® data regions now run on AWS. U.S. data stays in Northern Virginia, and European data stays in the EU, in Frankfurt.
A former police commander with 26 years of police service, 18 of them in command. He founded the Trinity Guard® brand in 2022 and holds qualifications as an electronics technician and a security systems installer.
DigitalGuardTour.com uses essential cookies and similar technologies
to operate this website, remember your choice, and help protect forms from spam or abuse.
Optional analytics starts only if you allow it.
Essential operation
Required for basic site functionality, remembering your cookie choice,
and form security. This cannot be turned off.
Always active
Site analytics
Helps us understand which pages are visited, what devices are used,
and how visitors find the website. This is enabled only with your consent.