The ultimate security solution for mobile apps
Leave attackers nowhere to strike
Add the SDK to defend against CC (HTTP flood) and DDoS attacks, prevent DNS poisoning and traffic hijacking, and keep your origin hidden. When attacks hit, your business stays online.
Android supported, iOS in development
Three things the usual setup cannot stop
Domains and endpoints are easy to find
Capture the app's traffic once and the domains and API endpoints are all there. Attackers simply aim at them, and switching domains only buys a few days.
An exposed origin IP is hard to hide again
DNS history, certificates and email headers can all leak the origin address. Attackers go around the protection and hit the origin directly.
Attack requests look like normal ones
Requests that imitate real API calls are hard to tell apart with rules. Loose rules let them through, strict rules block real users.
Features
A complete layer of protection designed for the request path of a mobile app
Private encrypted protocol
Our own private protocol, encrypted end to end. Captures reveal nothing, and traffic cannot be forged or replayed.
No public domain
Access does not depend on a public domain, so attackers have nothing to aim at. Routes are delivered dynamically and verified all the way, so they cannot be forged or hijacked.
Attack isolation
Different devices take different routes. When a route is attacked, the impact stays within a small scope and other users are not affected.
Automatic failover
When a route has trouble, traffic switches automatically and requests are retried. Users do not notice.
Invisible origin
Your origin address never appears in the app and is not visible from outside. The protection network reaches it on your behalf.
Device bans in seconds
Spot an abnormal device and ban it in the console with one click. It takes effect everywhere within seconds, with no app release.
Live statistics
Requests, traffic, active devices and error rate, by app and time range.
Multiple apps and members
Manage several apps under one account, with admin and read-only roles for members.
How it works
Management and traffic are independent, so console maintenance does not affect your app
-
1
Add the SDK
A few lines of code and you are integrated. Your business code stays the same, and you can route only selected requests through the channel.
-
2
A dedicated channel opens
An encrypted channel is set up between your app and the protection network. Only your app can enter it.
-
3
Filter and forward
Requests are verified and filtered, then forwarded to your origin, which still receives the real client IP.
-
4
Manage everything in the console
Apps, origins and banned devices are managed in the console, and changes take effect everywhere within seconds.
Integrate in three steps
After activation, get your integration parameters in the console and start
- 1 Create an app in the console and add your origins
- 2 Add the SDK to your app and fill in the parameters
- 3 Add the interceptor to your OkHttpClient and release
- Android (OkHttp) supported
- iOS in development
- Contact us about other frameworks
// Get the integration parameters in the console
val xwaf = Xwaf.create(context, config)
val client = OkHttpClient.Builder()
.addInterceptor(xwaf.interceptor())
.build()
Pricing
A flat monthly fee. Each plan includes app licenses, requests, concurrency and bandwidth, with no limit on daily active devices
Lite
Shared nodes, for getting a small workload running
- 1 app license
- 3M requests per day
- 200 concurrent requests
- Shared bandwidth from 30 Mbps
- Shared node pool
Starter
Shared nodes with higher limits, for a growing app
- 1 app license
- 10M requests per day
- 600 concurrent requests
- Shared bandwidth from 50 Mbps
- Shared node pool
Growth
Dedicated nodes with more bandwidth and protection, plus dedicated support
- 1 app license
- 20M requests per day
- 1,200 concurrent requests
- Shared bandwidth from 100 Mbps
- 20 dedicated nodes (expandable)
Professional
Dedicated nodes, for one app in production
- 1 app license
- 30M requests per day
- 2,000 concurrent requests
- Shared bandwidth from 100 Mbps
- 20 dedicated nodes (expandable)
Enterprise
Several apps, dedicated bandwidth, and higher request and concurrency limits
- 3 app licenses
- 60M requests per day
- 4,000 concurrent requests
- Dedicated bandwidth from 50 Mbps
- 20 dedicated nodes (expandable)
Custom
Limits, nodes and bandwidth tailored to you
- Limits, nodes and bandwidth tailored to you
Frequently asked questions
Do I need a domain? +
No. Access does not depend on a public domain.
Which platforms are supported? +
Android (OkHttp) is available now and iOS is in development. If you use another networking stack, contact us and we will take a look.
Does all traffic have to go through the channel? +
No. You can route only selected hosts through it. For video and large downloads we suggest staying on your CDN.
Does a console outage affect my app? +
No. Management and traffic are independent, so your app keeps running during console maintenance.
How are requests and concurrency counted? +
The request limit is per day. It counts the HTTP requests passing through the nodes each day and resets at 00:00 Beijing time. Concurrency is the number of requests in progress at the same moment, per app. We contact you in advance when you approach a limit.
How do I get started? +
Send the contact form. Once we set up your account, you can create apps in the console and get the integration parameters.
Ready to put a layer of protection in front of your app?
Tell us the size of your app and the problems you see, and we will help you pick a plan
Contact us