Legal · Last updated May 4, 2026
How Vibely meters work, what your plan includes, and the limits we apply to keep things fast for everyone.
Vibely meters work in credits. A credit is consumed each time the agent finishes a turn (one streamText round-trip), with cost weighted by the model selected. All plans receive a monthly credit allowance that resets on your billing cycle date.
Each project runs in an isolated E2B sandbox with its own filesystem and dev server. Sandboxes are recycled after a period of inactivity to keep the platform fast and secure.
Preview URLs at *.vibelyagent.com are public-readable by default. Use private visibility for projects you don’t want indexed.
We apply per-user, per-project, and per-IP rate limits to keep the platform responsive for everyone.
Project files, snapshots, and message history are stored in Supabase. Inactive previews may be paused; redeploys are instant. Deleted projects are purged within 30 days.
Vibely is a creative tool, not a hosting platform for arbitrary workloads. Long-running background jobs, mining, or production traffic that exceeds preview-class usage should move to your own infrastructure (export via GitHub or Download).
Connectors (Supabase, GitHub, Stripe, etc.) operate against your own credentials and are billed by the third-party service. Vibely does not proxy or aggregate connector calls.
If you exceed your plan limits, we will notify you in product and offer to upgrade or apply pay-as-you-go credits. We may temporarily throttle or suspend accounts that show signs of abuse (e.g. mining, mass-scraping, spam generation).
Limits and rates may evolve as the underlying compute and model costs change. We give at least 14 days’ notice before reducing any included allowance on a paid plan.