FAQs
FAQs
Frequently Asked Questions
Find clear answers about our browser infrastructure, pricing, and how to get started.
General Questions
Learn more about dat.ai, how our browser infrastructure operates behind the scenes, and how it helps teams automate the web.
Can you explain browser profile creation in more detail? What should users consider when creating a task?
Currently, for beta testing, we copy the actual user profile from the device for authenticity. In production, profiles are created automatically for each task. We can also create persistent profiles for specific clients—these stay on the user's side and can be reused across tasks. Let us know your requirements.
Can you explain browser profile creation in more detail? What should users consider when creating a task?
Currently, for beta testing, we copy the actual user profile from the device for authenticity. In production, profiles are created automatically for each task. We can also create persistent profiles for specific clients—these stay on the user's side and can be reused across tasks. Let us know your requirements.
Does the browser close after task execution? Can sessions be reused for subsequent tasks?
The browser closes after each task to avoid consuming memory and CPU on the end device. If you need persistent sessions for your use case, contact us—we're flexible on customizations.
Does the browser close after task execution? Can sessions be reused for subsequent tasks?
The browser closes after each task to avoid consuming memory and CPU on the end device. If you need persistent sessions for your use case, contact us—we're flexible on customizations.
What is DAT?
We're the infrastructure layer for distributed web automation. Run browsers on edge devices across regions—no proxies, no centralized bottlenecks, no infrastructure to manage.
What is DAT?
We're the infrastructure layer for distributed web automation. Run browsers on edge devices across regions—no proxies, no centralized bottlenecks, no infrastructure to manage.
What problem do you solve?
Web access for automation breaks when you scale. Cloudflare blocks. Regional endpoints timeout. GDPR compliance gets complicated. We handle the infrastructure so you don't have to.
What problem do you solve?
Web access for automation breaks when you scale. Cloudflare blocks. Regional endpoints timeout. GDPR compliance gets complicated. We handle the infrastructure so you don't have to.
What stage are you at?
Early-stage growth. We're building with our first customers. Your feedback shapes the product.
What stage are you at?
Early-stage growth. We're building with our first customers. Your feedback shapes the product.
How can I join the beta testing program?
We’re actively onboarding early partners. To join the beta email us at es@dat.ai or sign up via the "Get started" links below.
How can I join the beta testing program?
We’re actively onboarding early partners. To join the beta email us at es@dat.ai or sign up via the "Get started" links below.
What kind of use cases are you looking for in beta partners?
We're particularly interested in: - Travel and booking companies (price monitoring, regional pricing, competitor intelligence) - Teams building AI agents that need reliable web access - Companies expanding into GDPR-compliant markets - Development teams replacing complex scraping infrastructure - Anyone automating web workflows across multiple geographic regions If your use case involves web automation that breaks on Tuesday afternoons when Cloudflare updates, or you're spending too much engineering time maintaining scrapers—we want to talk to you.
What kind of use cases are you looking for in beta partners?
We're particularly interested in: - Travel and booking companies (price monitoring, regional pricing, competitor intelligence) - Teams building AI agents that need reliable web access - Companies expanding into GDPR-compliant markets - Development teams replacing complex scraping infrastructure - Anyone automating web workflows across multiple geographic regions If your use case involves web automation that breaks on Tuesday afternoons when Cloudflare updates, or you're spending too much engineering time maintaining scrapers—we want to talk to you.
What's the difference between dat.ai and traditional scraping services or proxy providers?
We're infrastructure, not a data service. Traditional approaches use centralized cloud servers routing through proxy chains. We run real browsers on edge infrastructure—geographically distributed across actual devices. This means: - No proxy layer (fewer points of failure) - True regional execution (not simulated via proxies) - Lower latency for geo-specific tasks - Real browser fingerprints (harder to detect) - Serverless pricing model (not per-GB)
What's the difference between dat.ai and traditional scraping services or proxy providers?
We're infrastructure, not a data service. Traditional approaches use centralized cloud servers routing through proxy chains. We run real browsers on edge infrastructure—geographically distributed across actual devices. This means: - No proxy layer (fewer points of failure) - True regional execution (not simulated via proxies) - Lower latency for geo-specific tasks - Real browser fingerprints (harder to detect) - Serverless pricing model (not per-GB)
Do you support headless browsers or only real browsers?
We run real browsers, not headless automation that gets flagged. This is why we have higher success rates with anti-bot systems.
Do you support headless browsers or only real browsers?
We run real browsers, not headless automation that gets flagged. This is why we have higher success rates with anti-bot systems.
What about API rate limits?
We're still finalizing rate limit policies for general availability. Early beta partners are on custom terms. Contact us to discuss your expected volume.
What about API rate limits?
We're still finalizing rate limit policies for general availability. Early beta partners are on custom terms. Contact us to discuss your expected volume.