README
¶
Customer Data Platform for Developers
Table of Contents
- What is RudderStack?
- Why use RudderStack?
- Set up RudderStack
- Our customers
- Contribute to RudderStack
- Follow us
What is RudderStack?
As the leading open-source Customer Data Platform (CDP), RudderStack provides data pipelines that make it easy to collect data from every application, website and SaaS platform, then activate it in your warehouse and business tools.
With RudderStack, you can build customer data pipelines that connect your whole customer data stack and then make them smarter by triggering enrichment and activation in customer tools based on analysis in your data warehouse. Its easy-to-use SDKs and event source integrations, Cloud Extract integrations, transformations, and expansive library of destination and warehouse integrations makes building customer data pipelines for both event streaming and cloud-to-warehouse ELT simple.
Questions? Join our Slack channel for support on the product.
| Try RudderStack Cloud Free - a free tier of RudderStack Cloud. Click here to start building a smarter customer data pipeline today, with RudderStack Cloud. |
|---|
Why use RudderStack?
-
Unlimited Events: Event volume-based pricing of most of the commercial systems is broken. With RudderStack, you are be able to collect as much data as possible without worrying about overrunning your event budgets.
-
Warehouse-first: RudderStack treats your data warehouse as a first class citizen among destinations, with advanced features and configurable, near real-time sync.
-
Developer-focused: RudderStack is built API-first. It integrates seamlessly with the tools that the developers already use and love.
-
Segment API Compatible: RudderStack is Segment API compatible. So you don't need to change your app if you are using Segment, just integrate the RudderStack SDKs into your app and your events will keep flowing as before (including data-warehouse).
-
Production-ready: Companies like Mattermost, IFTTT, Torpedo, Grofers, 1mg, Nana, OnceHub, and dozens of large companies use RudderStack for collecting their events. Note: If you're using RudderStack and would like to add your name in this list, please submit a PR.
-
Seamless Integration: RudderStack currently supports integration with over 80 popular tool and warehouse destinations.
-
User-specified Transformation: RudderStack offers a powerful JavaScript-based event transformation framework which lets you enhance or transform your event data by combining it with your other internal data. Furthermore, RudderStack runs inside your cloud or on-premise environment, so you can easily access your production data to join with the event data.
-
High Availability: RudderStack comes with at least 99.99% uptime. We have built a sophisticated error handling and retry system that ensures that your data will be delivered even in the event of network partitions or destinations downtime.
-
Privacy and Security: You can collect and store your customer data without sending everything to a third-party vendor. With RudderStack, you get fine-grained control over what data to forward to which analytical tool.
Our customers
Get started with RudderStack
The easiest way to experience RudderStack is to sign up for RudderStack Cloud Free - a completely free tier of RudderStack Cloud. Click here to get started.
You can also set up RudderStack on your platform of choice with these two easy steps:
Step 1: Set up RudderStack
| If you are planning to use RudderStack in production, we STRONGLY recommend using our Kubernetes Helm charts. We update our Docker images with bug fixes much more frequently than our GitHub repo. |
|---|
Step 2: Verify the installation
Once you have installed RudderStack, send test events to verify the setup.
UI pages
Connections page
Live events
Connecting a RudderStack source to a destination
RudderStack architecture
Read about RudderStack's architecture in our wiki.
License
RudderStack server is released under the AGPLv3 License.
Contribute
We would love to see you contribute to RudderStack. Get more information on how to contribute here.
Follow us
👏 Our Supporters
Documentation
¶
There is no documentation for this package.
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
Package admin : - has a rpc over http server listening on a unix socket - support other packages to expose any admin functionality over the above server Example for registering admin handler from another package // Add this while initializing the package in setup or init etc.
|
Package admin : - has a rpc over http server listening on a unix socket - support other packages to expose any admin functionality over the above server Example for registering admin handler from another package // Add this while initializing the package in setup or init etc. |
|
gomock_reflect_841618232
command
|
|
|
build
|
|
|
wait-for-go
command
|
|
|
* Handling HTTP requests to expose the schemas *
|
* Handling HTTP requests to expose the schemas * |
|
mocks
|
|
|
app
Package mock_app is a generated GoMock package.
|
Package mock_app is a generated GoMock package. |
|
config/backend-config
Package mock_backendconfig is a generated GoMock package.
|
Package mock_backendconfig is a generated GoMock package. |
|
jobsdb
Package mocks_jobsdb is a generated GoMock package.
|
Package mocks_jobsdb is a generated GoMock package. |
|
logger
Package mocks is a generated GoMock package.
|
Package mocks is a generated GoMock package. |
|
processor/transformer
Package mocks_transformer is a generated GoMock package.
|
Package mocks_transformer is a generated GoMock package. |
|
rate-limiter
Package mocks_ratelimiter is a generated GoMock package.
|
Package mocks_ratelimiter is a generated GoMock package. |
|
router
Package mock_network is a generated GoMock package.
|
Package mock_network is a generated GoMock package. |
|
router/transformer
Package mocks_transformer is a generated GoMock package.
|
Package mocks_transformer is a generated GoMock package. |
|
services/debugger
Package mock_debugger is a generated GoMock package.
|
Package mock_debugger is a generated GoMock package. |
|
services/dedup
Package mock_dedup is a generated GoMock package.
|
Package mock_dedup is a generated GoMock package. |
|
services/filemanager
Package mock_filemanager is a generated GoMock package.
|
Package mock_filemanager is a generated GoMock package. |
|
utils
Package utils is a generated GoMock package.
|
Package utils is a generated GoMock package. |
|
utils/logger
Package mock_logger is a generated GoMock package.
|
Package mock_logger is a generated GoMock package. |
|
utils/sysUtils
Package mock_sysUtils is a generated GoMock package.
|
Package mock_sysUtils is a generated GoMock package. |
|
utils/types
Package mock_types is a generated GoMock package.
|
Package mock_types is a generated GoMock package. |
|
proto
|
|
|
services
|
|
|
helpers/tomlmerge
command
|
|
|
load
command
|
|
|
main
command
package to locally test load using helpers
|
package to locally test load using helpers |
|
logger
Logger Interface Use instance of logger instead of exported functions usage example import ( "errors" "github.com/rudderlabs/rudder-server/utils/logger" ) var log logger.LoggerI = &logger.LoggerT{} or var log logger.LoggerI = logger.NewLogger() ...
|
Logger Interface Use instance of logger instead of exported functions usage example import ( "errors" "github.com/rudderlabs/rudder-server/utils/logger" ) var log logger.LoggerI = &logger.LoggerT{} or var log logger.LoggerI = logger.NewLogger() ... |
|
sysUtils
Zip & Gzip Interfaces Use this instead of archive/zip and compress/gzip packages.
|
Zip & Gzip Interfaces Use this instead of archive/zip and compress/gzip packages. |
|
tests/GA
command
|
|