In this document, you'll learn about our vision, and how rake.red uses accounts, projects, and forms to structure your data.
We started to work on rake.red, because current solutions are expensive, or hard to configure. With rake.red we provide a solution where collecting user data is a smooth and affordable experience.
You'll need an account to get started. The management portal of rake.red is not accessible without one. You can create an account for yourself, and manage all data by yourself. Or invite your team members to create accounts as well. They can be invited via the project settings, so that you can collaborate on the data without the need to export it first.
Don't worry, forms can still be submitted without logging in. The visitors of your site don't need to log in, and they don't need to know that you're using rake.red to handle your form submissions.
Rake.red groups forms by project. You can see a project as your website, but we don't want to call it
sites, because a form is not always connected to a website. Think of quick surveys that you share on social media, or a lead form that you use for public events.
Project names are unique throughout rake.red. That means that there can only be one
my project, and only one
other project. This is because we use your project names in the api url that you'll be using. For convenience.
For example, if you'd name your project
my project, we will generate a slug like
my-project. That slug, will be used in your api url like:
Forms are created inside projects. They have a unique name on a project level. So you can create a "contact" form in "my project" as well as "another project", but you can't create two forms named "contact" in the same project. This is because here as well the name is used in the generated endpoint. If you have a project named "my project" and create a form named "contact", the endpoint that you'll need to add to your form action will be:
And let's be honest, if it weren't for the URL. It would be highly confusing. Two contact forms in one project (website) that have their results stored in a different location?
User data is stored in forms, a project is a group of forms, and accounts provide access to projects. There is a many:many relationship between accounts and projects. And a one:many relationship between projects and forms.