Every event in your database, streamed anywhere.
grovs writes every click, install, open, message and purchase to data stores you run. Query it directly, stream it to your warehouse, or export it.
Events today
4.82M
Delivered
100%
Lag
1.2s
Retention
13 months
| Destination | Status | Throughput |
|---|---|---|
| HTTPS endpointingest.yourcompany.com/grovs | Streaming | 4,812 / min |
| S3 buckets3://analytics-raw/grovs/ | Streaming | JSON lines · gzip |
| Pull feedCursor · token | Ready | warehouse job |
Live events
- link_opengo.medly.app/refilliOSnow
- install_attributedgo.medly.app/rx/newAndroid1s
- purchase_validatedpremium_yearlyiOS2s
- push_openedrefill_reminderiOS3s
-- your ClickHouse
SELECT event, count()
FROM grovs.events
WHERE ts > now() - 7d
GROUP BY event
link_open284,112
session_start1.9M
purchase_validated3,418
push_opened41,920
How it works.
- 1
Events land in your database
Every click, install, open, message and purchase is written to your own data stores.
- 2
Query or stream
Use SQL directly, stream to an HTTPS endpoint or S3, or pull with a cursor.
- 3
Keep what you need
Set retention per project, export history, and build on a stable, versioned format.
What your data does for you.
Already in your database.
Every event and every setting is written to data stores you run. Nothing to request.
Your cloud
grovs
Config store
links, campaigns
Event store
every event
Streamed where you need it.
Send events as they happen to an HTTPS endpoint or S3-compatible storage, with replay.
Event stream
4,812 events / min
HTTPS endpointLive
ingest.yourcompany.comS3 bucketLive
s3://analytics-raw/grovsBuilt for your systems.
A REST API for links, events, audiences and campaigns, plus a cursor-based pull feed.
POST /v1/links
{ "path": "/refill",
"data": { "screen": "RefillOrder" },
"fallback": "https://medly.com/refill" }
→ 201 go.medly.app/refillEvery feature.
Included on every grovs plan, cloud or self-hosted.
| Storage | Delivery | Access | Control |
|---|---|---|---|
| Your event storeEvery event, unsampled. | HTTPS streamEvents to your endpoint as they happen. | SQLQuery your data directly. | Your infrastructureNothing leaves unless you send it. |
| Your config storeLinks, campaigns and audiences. | S3 exportTo S3-compatible storage. | REST APILinks, events, audiences, campaigns. | Token accessScoped tokens for every consumer. |
| Retention controlsChoose how long raw events stay. | ReplayResend from an earlier point. | Pull feedRead after a cursor you keep. | Self-hosted or cloudSame data model either way. |
| DeletionRemove a user's data on request. | Versioned formatStable envelope with event ids. | ExportsDate-bounded exports and CSV. | MonitoringDelivery status per destination. |
Storage
- Your event storeEvery event, unsampled.
- Your config storeLinks, campaigns and audiences.
- Retention controlsChoose how long raw events stay.
- DeletionRemove a user's data on request.
Delivery
- HTTPS streamEvents to your endpoint as they happen.
- S3 exportTo S3-compatible storage.
- ReplayResend from an earlier point.
- Versioned formatStable envelope with event ids.
Access
- SQLQuery your data directly.
- REST APILinks, events, audiences, campaigns.
- Pull feedRead after a cursor you keep.
- ExportsDate-bounded exports and CSV.
Control
- Your infrastructureNothing leaves unless you send it.
- Token accessScoped tokens for every consumer.
- Self-hosted or cloudSame data model either way.
- MonitoringDelivery status per destination.
Questions about a feature?
Talk to an engineer who builds it, or read how it works in the docs.
Runs on your servers.
Data is part of the grovs deployment in your cloud or data center. Or start on grovs Cloud and move later.
Stays in your cloud
Everything. Configuration and events stay in your data stores.
What leaves
Only what you send to destinations you configure.
One SDK, five products.
Each product is one step of the same journey: bring users in, understand them, keep them, monetize and own the data.
Questions, answered.
Something else? Talk to an engineer.
Where exactly does our data live?
In the Postgres and ClickHouse you run, inside your cloud or data center. On grovs Cloud it lives in a dedicated project for your account.
Do you support Snowflake or BigQuery?
Stream events to S3 or an HTTPS endpoint and load them from there with the tools you already use. Direct warehouse destinations are available on request.
Is the event format stable?
Yes. Events use a versioned envelope, and every event has an id so consumers can deduplicate safely.
What if our consumer goes down?
The stream keeps a cursor per destination. When your endpoint comes back, delivery resumes from where it stopped, and you can replay from an earlier point if you need to.
Can we delete a user's data?
Yes. Deleting a user removes their events and profile, which supports GDPR and similar requests.
How long are events kept?
You choose a retention period per project. Raw events older than that are removed automatically.
Your first link, live this afternoon.
Install the SDK, connect your domain and send a link that opens the right screen. Start free on grovs Cloud, or run the same stack in your own.
Compare plans$0up to 10K monthly users
- Sign up and add the SDK
- Your first link live the same day
- Flat yearly price as you grow
Flat licencea year, in your cloud, no metering
- AWS, Azure, GCP or your data center
- Deployment help from our engineers
- Your SSO, your database, your rules