Signup form protection quick start
Arcjet signup form protection combines rate limiting, bot protection, and email validation to protect your signup forms from abuse.
What is Arcjet?
Arcjet helps developers protect their apps in just a few lines of code. Bot detection. Rate limiting. Email validation. Attack protection. Data redaction. A developer-first approach to security.Quick start
This guide will show you how to protect your
1. Install Arcjet SDK
In your project root, run the following command to install the SDK:
2. Set your key
Create a free Arcjet account then follow the
instructions to add a site and get a key. Add it to a .env.local
file in your
Since NODE_ENV
for you, you also
need to set ARCJET_ENV
in your environment file. This allows Arcjet to accept
a local IP address for development purposes.
Since NODE_ENV
for you, you also
need to set ARCJET_ENV
in your environment file. This allows Arcjet to accept
a local IP address for development purposes.
Since NODE_ENV
for you, you also
need to set ARCJET_ENV
in your environment file. This allows Arcjet to accept
a local IP address for development purposes.
3. Protect a form
Arcjet signup form protection is a combination of the rate limiting, bot protection, and email validation primitives. These are configured using our recommended rules.
The example below is a simple email form. You could adapt this as part of a signup form.
Create the Svelte page containing the form:
Next, create the server-side code to handle the page submission:
Create a new route at app/routes/arcjet.tsx
with the contents:
Create the API route handler to receive the form submission:
Next, create the form page:
Next, create the form page:
Next, create the form page:
Next, create the form page:
Several files are combined here to demonstrate creating a form handler controller. In a real application you should split them as suggested in the comments.
4. Start app
Start your app and load http://localhost:3000/form
. Submit the form with a
variety of email addresses and you can see how the check behaves. The requests
will also show up in the Arcjet dashboard.
4. Start app
Start your app and load http://localhost:5173/form
. Submit the form with a
variety of email addresses and you can see how the check behaves. The requests
will also show up in the Arcjet dashboard.
4. Start server
Make a curl
POST
request from your terminal to your application with various
emails to test the result.
4. Start app
Make a curl
POST
request from your terminal to your application with various
emails to test the result.
4. Start server
Make a curl
POST
request from your terminal to your application with various
emails to test the result.
4. Start app
Make a curl
POST
request from your terminal to your application with various
emails to test the result.
The requests will also show in the Arcjet dashboard.
FAQs
Do I need to run any infrastructure e.g. Redis?
No, Arcjet handles all the infrastructure for you so you don't need to worry about deploying global Redis clusters, designing data structures to track rate limits, or keeping security detection rules up to date.
What is the performance overhead?
Arcjet SDK tries to do as much as possible asynchronously and locally to minimize latency for each request. Where decisions can be made locally or previous decisions are cached in-memory, latency is usually <1ms.
When a call to the Arcjet API is required, such as when tracking a rate limit in a serverless environment, there is some additional latency before a decision is made. The Arcjet API has been designed for high performance and low latency, and is deployed to multiple regions around the world. The SDK will automatically use the closest region which means the total overhead is typically no more than 20-30ms, often significantly less.
What happens if Arcjet is unavailable?
Where a decision has been cached locally e.g. blocking a client, Arcjet will continue to function even if the service is unavailable.
If a call to the Arcjet API is needed and there is a network problem or Arcjet is unavailable, the default behavior is to fail open and allow the request. You have control over how to handle errors, including choosing to fail close if you prefer. See the reference docs for details.
How does Arcjet protect me against DDoS attacks?
Network layer attacks tend to be generic and high volume, so these are best handled by your hosting platform. Most cloud providers include network DDoS protection by default.
Arcjet sits closer to your application so it can understand the context. This is important because some types of traffic may not look like a DDoS attack, but can still have the same effect. For example, a customer making too many API requests and affecting other customers, or large numbers of signups from disposable email addresses.
Network-level DDoS protection tools find it difficult to protect against this type of traffic because they don't understand the structure of your application. Arcjet can help you to identify and block this traffic by integrating with your codebase and understanding the context of the request e.g. the customer ID or sensitivity of the API route.
Volumetric network attacks are best handled by your hosting provider. Application level attacks need to be handled by the application. That's where Arcjet helps.
What next?
Get help
Need help with anything? Email us or join our Discord to get support from our engineering team.