1. What this page is
These Product Terms are part of our Terms of Service. They cover the parts of Vibely that change as the product changes — plans, credits, limits, previews, publishing, mobile builds and connectors — so the Terms themselves stay short enough to read.
Everything here is subject to the Terms of Service: the same definitions, the same limitation of liability, and the same governing law — the governing law and forum clause in the Terms of Service at /terms-of-service applies to this page as written there, and is not restated here. Where this page and the Terms of Service genuinely conflict, the Terms of Service win.
2. Plans
Four tiers. All prices are in US dollars. A yearly plan is billed at ten months of the monthly price.
- Free — 5 credits a month, web app generation, unlimited projects, public deploys on a vibelyagent.com subdomain, community support. The monthly grant tops your balance up to 5; it does not accumulate. Free does not include mobile app generation, custom domains, or team roles.
- Pro — from 100 credits a month, scaling to 10,000, at $25 a month or $250 a year. Adds native mobile generation for iOS and Android, custom domains, credit top-ups, and rollover.
- Business — from 100 credits a month, scaling to 10,000, at $50 a month or $500 a year. Adds unlimited seats, a shared workspace credit pool, roles (Owner, Admin, Editor, Viewer), SSO through SAML or Google Workspace, SCIM provisioning, the security center and audit log, and private, workspace-only and group-only publishing.
- Enterprise — arranged case by case. Write to [email protected] or use the form at /contact-sales. Enterprise terms are at /enterprise-terms and the availability commitment for paid plans is at /sla; an Order form is drawn up case by case.
3. Prices and tax
All plans are billed in USD, worldwide; what that costs in your own currency depends on your bank’s exchange rate, which is not a price set by us. Prices exclude any tax that applies where you are; you are responsible for it. We do not calculate or collect tax at checkout. We will not change your price during a period you have already paid for, and we give at least 30 days’ notice before an increase takes effect. Subscriptions renew automatically until you cancel; there is no cancellation deadline, and cancelling stops the next charge without shortening the period you have already paid for. The refund rule, and what cancelling and termination do to your credits, are in the Terms of Service at /terms-of-service under “Refunds and cancellation”.
4. What a credit is
A credit is the prepaid unit in which we meter and charge agent work. Credits are granted monthly with your plan and may be purchased as top-ups on a paid plan. They are non-refundable, are not redeemable for cash, and are not transferable between workspaces. They have no cash value. Credits granted with a plan, or given free as a promotion, can expire and can be withdrawn, and are spendable only while the plan is active; credits you bought as a top-up do not expire on a clock and stay spendable after the plan ends, lasting until you spend them or the account ends.
A turn is charged for the tokens it actually used, priced by the model selected, subject to a small per-turn minimum. The minimum for a build turn is 0.5 credits. There is no per-turn ceiling: a heavy turn is charged what it actually cost, not clamped to a flat cap. On the model we publish our band against, a trivial turn costs 0.50 credits, a mid-sized one about 0.91, a large one about 3.39 and a heavy one about 6.79.
Some tools add a fixed surcharge on top of the model cost, per call: image generation 0.1 credits, video generation 0.2, web scraping 0.05, web search 0.02, image search 0.02.
5. When a credit is not consumed
Three cases cost you nothing:
- A turn the agent runs to fix its own error is free.
- A build turn that ran no tools is free — it produced no diff and executed nothing, so we bill nothing.
- A very small chat turn, under about a fifth of a US cent of model spend, is free.
6. Our metering is the record
We use reasonable efforts to meter usage accurately. Metering depends in part on third-party model and infrastructure providers. Our usage and billing records, and our payment processor’s records, are the evidence we start from and the figures we bill on. They are not the last word: raise a charge you think is wrong by emailing [email protected] within 30 days of the charge date, send us what you have, and we weigh your evidence alongside ours and tell you what we found. Nothing here makes our records binding on you, and nothing here limits any right you have as a consumer under the law that applies to you.
7. Rollover, top-ups and running out
On a paid plan, credits you have not spent when the cycle renews roll over once: they stay spendable through the following cycle and expire at the end of it. We spend rolled-over credits before your new grant, so the ones that expire soonest go first. On the Free plan the monthly grant tops up to the allowance rather than accumulating.
Top-ups are available on paid plans in blocks of 100, 200, 400 or 800 credits, at $0.25 per credit on Pro and $0.50 per credit on Business. A top-up is prepaid and non-refundable like any other credit, but unlike plan credits it runs on no clock: a renewal does not reset it, cancelling does not forfeit it, and it is spent only after your plan credits and rollover are exhausted. It lasts until you spend it or the account ends — see /terms-of-service for what termination and deletion do.
When your balance reaches zero the agent stops accepting new turns in that workspace until your cycle renews or you buy a top-up. Nothing is deleted: your projects, source code, previews and published apps are unaffected by a zero balance.
8. Fair use, limits and concurrency
Credits are the limit that matters — they meter the expensive part, so we do not sell a seat and then throttle it by the hour. We do apply protective limits to keep the platform up: request rate limits on our API and on package installs inside sandboxes, and limits on how many sandboxes one workspace can run at once. We have not published numbers for these, and you should not design around a specific one. If a protective limit is getting in the way of legitimate work, email [email protected] and we will look at it. Automated or scripted use that exists to drain credits, mine the models, or degrade the service for others is a breach of the Acceptable Use Policy.
9. Projects and sandboxes
Every plan, including Free, can create unlimited projects. Each project runs in its own isolated cloud sandbox with its own filesystem and dev server. A sandbox is paused after inactivity and discarded 72 hours later; the project itself is not lost, it resumes from a snapshot or from the files held in our database the next time you open it. The first turn after a resume is slower than one on a warm sandbox.
10. What you own, and what output is not warranted to be
Who owns generated code, the carve-out for third-party rights in the underlying AI models, the warranty you give us about what you submit, and the fact that output is not warranted to be accurate, original or secure are all set out in the Terms of Service at /terms-of-service. Nothing on this page adds to or narrows any of it. The indemnity we give runs to paid plans and covers the Vibely Platform only — never generated output.
11. Beta Features
A Beta Feature is any feature, model, connector or template we make available and identify as alpha, beta, preview, early access or experimental. A Beta Feature is provided as-is, may change or be withdrawn without notice, is excluded from any service commitment we may make, and consumes credits like any other work. Do not build something you depend on around a Beta Feature without a fallback.
12. Preview environments
A preview is the live view of a project while you are building it, served from the project sandbox on a vibelyagent.com host. It is ephemeral. It pauses when you stop working, it is discarded 72 hours after it pauses, and it is not built for production traffic. Do not point real users, a status page, a webhook receiver or a cron job at a preview URL.
Web previews are cookie-gated by default, so a signed-out stranger with the link does not get in. Two things change that, and you should know both: turning on public remixing opens the preview to anyone with the link, and mobile previews opened through Expo are exempt from the cookie gate, so for those the unguessable preview host is the only thing protecting them. Treat a mobile preview link as a secret.
13. Published apps and hosting
Publishing takes a build of your project and serves it from our infrastructure, either on a subdomain of vibelyagent.com or on a custom domain you connect. We host the build and its static assets. We do not host a database, a backend or a background worker for your app — those run on services you connect yourself, under your own accounts, and you are responsible for them.
That includes anything a form in your app collects. We do not store your end users' form submissions: they go wherever your app sends them — the database or service you connected — and the retention, the deletion and the lawful basis for them are yours to set there. The 730-day retention published in our Privacy Policy at /privacy-policy and our Data Processing Agreement at /dpa is for forms on vibely.sh itself, such as our own contact and sales forms. Do not plan your own retention around it.
A published app has one of four visibility settings: public; workspace, where only signed-in members of your workspace can reach it; groups, where only members of the groups you pick can reach it; and private, where only you can. Workspace, groups and private publishing are Business-plan capabilities. On Free and Pro a published app is public.
We can suspend or take down a published app that breaches the Acceptable Use Policy, or that we are required to remove by law or by a valid legal request. Where we can, we tell you first and give you a chance to fix it. Where the breach is serious — phishing, malware, CSAM, an active attack on someone else — we act first and tell you afterwards.
14. Custom domains
Pro and Business plans can connect a domain you control. Connecting a domain routes it through our DNS and certificate setup; the domain registration itself stays yours, at your registrar, and renewing it is your job. If you register or transfer a domain through Vibely, the Domain Registration Terms at /domain-terms govern that registration and the registrar’s own policies apply on top. A domain that expires, or whose DNS you change, takes your published app down with it, and we cannot restore it for you.
15. Native mobile builds
Vibely generates Expo and React Native apps and builds them through the EAS build pipeline. Submission to the Apple App Store and Google Play happens under your own Apple and Google developer accounts. You open those accounts, you pay their fees, and you accept their agreements.
Whether your app is accepted is Apple’s and Google’s decision, not ours. We do not control review, we cannot appeal on your behalf, and a rejection, a removal or a policy change at either store is not a failure of the service and is not refundable. The same goes for a store account of yours that is suspended.
If your app sells digital goods or subscriptions used inside the app, the store rules require you to sell them through the store’s own in-app purchase system. Wiring a card payment form into a mobile app for digital goods is the most common reason a generated app gets rejected. Check the current App Store Review Guidelines and Google Play policies before you build the payment flow.
16. Connectors and third-party services
Connectors let your project talk to services you already use. They run against your own credentials and your own accounts: your usage is billed by that third party at their prices, and their terms govern what they do on their side. We do not proxy or aggregate connector calls.
We are not responsible for a third-party service being down, changing its API, changing its pricing, or closing your account there. If a connector stops working because the service behind it changed, we will fix our end as fast as we can, and credits you spent on turns in the meantime are still spent.
OAuth tokens for connectors you authorise are held by our connector gateway provider, Composio. The subprocessor list at /subprocessors names every vendor that processes data for us, what it is for, and where it processes.
17. Support
Free plans have community support. On a paid plan, email [email protected] for anything about billing, plans or credits, and [email protected] for privacy, security or abuse. We read both every business day.
The channels, the hours and our first-response targets by plan are published at /support-policy. Those response targets are targets, not commitments, and they carry no service credit. Availability is committed separately: the Service Level Agreement at /sla commits to 99.5% uptime on paid plans and carries service credits when we miss. If you need a contractual response time on top of that, write to [email protected].
18. Changes and deprecation
We give at least 14 days’ notice of material changes to these terms, by email or in-product notice, and at least 14 days’ notice before we reduce any credit allowance included in a paid plan.
Features change too. A Beta Feature can be withdrawn at any time, with no notice — that is what the beta label means. For anything that is not a Beta Feature, we will tell you before we withdraw it and give you a reasonable window to move off it; we have not yet fixed a published notice period for feature withdrawal, so do not plan around a specific number of days. Where we withdraw something you paid specifically to get, tell us and we will sort out the money.
19. Contact
Questions about plans, credits or limits? Email [email protected]. Questions about privacy or security? Email [email protected]. Vibely is operated by Mana Intelligence Private Limited, incorporated in India.