# Event Stream Sources


RudderStack's **Event Stream** product lets you collect the event data from all of your sites and applications and route it to a wide array of customer tools and data warehouses.

You can see how the product works in this self-paced product tour: 

<div style="position: relative; padding-bottom: calc(56.3603164942179% + 41px); height: 0; width: 100%;"><iframe src="https://demo.arcade.software/Kl1Y0goPxkfGwDR7F8ja?embed&embed_mobile=tab&embed_desktop=inline&show_copy_link=true" title="Collection and Integration (Event Stream) - Docs Page" frameborder="0" loading="lazy" webkitallowfullscreen mozallowfullscreen allowfullscreen allow="clipboard-write" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; color-scheme: light;" ></iframe></div>

The Event Stream product supports various SDKs and Cloud Apps as data sources listed below:

## SDKs

RudderStack provides the following open source SDKs for your web, mobile, and server-side applications:

### Web

Track customer event data from your website and web apps and send it to your specified destinations.

{{< sources category="web" >}}

### Mobile

Use the native RudderStack SDKs for the popular mobile operating systems and development frameworks.

{{< sources category="mobile" >}}

### Server

Use the server-side SDKs to track event data from your backend applications.

{{< sources category="server" >}}

## Cloud apps

Ingest event data from your cloud apps and route it to the specified destinations.

{{< sources category="webhook" >}}

## HTTP source

You can leverage the HTTP source to send events to RudderStack directly via HTTP API calls from your server-side applications.

{{< sources category="http" >}}

## Custom webhook

You can also add any source that supports a webhook, use it to ingest events, and send them to your preferred destinations via RudderStack. 

{{< sources category="custom webhook" >}}

## Required permissions

- [Admins]({{< ref "access-management/member-management.md#member-roles" >}}) have full access to create and manage Event Stream sources.
- [Members]({{< ref "access-management/member-management.md#member-roles" >}}) can have the following [permissions]({{< ref "access-management/policies-overview.md#resource-permissions" >}}) depending on their workspace policy:

| Permission | <div style="width:350px">Description</div> | 
| :----| :-----| 
| **Edit** |  Make changes to the configuration of Event Stream sources.  | 
| **Connect** | Connect an Event Stream source to a destination or Tracking Plan. | 
| **Create & Delete** | Create or delete Event Stream sources. | 

{{< warning >}}
To make a connection, that is, connect a source to a destination, the member must have both **Edit** and **Connect** permissions on both the resources.
{{< /warning >}}

{{< details "**Click here to see how these permissions appear in the workspace policy**." >}}
<br />

{{< figure src="images/access-management/event-stream.webp" alt="Permissions to manage Event Stream sources in RudderStack dashboard" >}}

{{< /details >}}
<br />

#### Permissions for legacy RBAC system

In the [legacy Permissions Management (RBAC) system]({{< ref "archive/dashboard-guides/user-management.md" >}}):

- [Org Admins]({{< ref "archive/dashboard-guides/user-management.md#organization-roles" >}}) and members with the [**Connections Admin** role]({{< ref "archive/dashboard-guides/user-management.md#connections" >}}) in their workspace policy can create and delete sources, and connect them to destinations
- Members with the [**Connections Editor** role]({{< ref "archive/dashboard-guides/user-management.md#connections" >}}) in their workspace policy can only edit the source configuration and connect sources to destinations

{{< image src="images/access-management/data-catalog-permissions-legacy-framework.webp" alt="Event Stream sources permissions in the legacy framework" >}}