Billing
Billing and subscription management
FAQs
What payment methods does Vibgrate accept?
Vibgrate accepts all major credit and debit cards including Visa, Mastercard, American Express, and Discover. Payments are processed securely through Stripe, a PCI-compliant payment processor. All transactions are charged in USD. For Enterprise plans, we can also accommodate invoicing and wire transfers upon request.
What is the difference between monthly and annual billing?
Monthly billing charges your card each month at the listed price. Annual billing charges once per year at a discounted rate — you get 20% off, the equivalent of 9.6 months of usage across the year. Vibgrate prices per billable project on a banded scale, so your annual total is simply your monthly estimate times 12, less 20%. Use the calculator on the pricing page to compare monthly and annual side by side. You can switch billing cycles at any time from your account settings.
Can I switch from monthly to annual billing?
Yes, you can switch from monthly to annual billing at any time from your account settings. When you switch, you'll receive a prorated credit for any unused time on your current monthly subscription, which is applied to your annual payment. The annual plan begins immediately and you'll start saving right away.
How do I update my payment information?
To update your payment method, log into Vibgrate Cloud at dash.vibgrate.com, navigate to Settings > Billing, and click 'Update Payment Method'. You can add a new card or update your existing card details. Changes take effect immediately. You'll also receive email notifications before any payment is processed.
How does proration work when I upgrade or downgrade my plan?
When you upgrade, you're charged immediately for the difference between your current plan and the new plan, prorated for the remaining time in your billing cycle. When you downgrade, you'll receive a credit toward future invoices for the unused portion of your current plan. Changes take effect immediately.
Where can I find my invoices and receipts?
All invoices and receipts are available in Vibgrate Cloud under Settings → Billing → History (dash.vibgrate.com/settings/billing/history). Open a row to download the Stripe PDF or receipt. Subscription invoices and one-off payments (including Relay credit top-ups) appear in the same list. Stripe also emails receipts to the billing email on file after each successful payment.
What currency is Vibgrate billed in, and is tax included?
All Vibgrate subscriptions are billed in US Dollars (USD). Prices shown on the pricing page are exclusive of tax. Depending on your location, applicable sales tax, VAT, or GST may be added to your invoice at checkout. Tax amounts are calculated automatically by Stripe based on your billing address.
How do I cancel my Vibgrate subscription?
To cancel, go to Vibgrate Cloud at dash.vibgrate.com, navigate to Settings > Billing, and click 'Cancel Subscription'. Your access continues until the end of your current billing period. You won't be charged again after cancellation. Your data is retained for 30 days after expiration in case you decide to resubscribe.
What is Vibgrate's refund policy?
We offer a full refund within 14 days of your initial purchase if you're not satisfied. For annual subscriptions, refund requests after 14 days are handled on a case-by-case basis with a prorated amount. To request a refund, contact support@vibgrate.com with your account details. Refunds are typically processed within 5-10 business days.
What happens if my payment fails?
If a payment fails, we'll notify you by email and automatically retry the charge after 3 days. We'll make up to 3 retry attempts over 9 days. During this time, your service continues uninterrupted. If all retries fail, your subscription will be paused until you update your payment method in Settings > Billing.
How does micro-project pricing work?
We don't bill every package as a full project. Each scanned project is automatically sized into one of four tiers — nano, micro, small or standard — and billed as a fraction of a project: standard counts as 1, small as one third (⅓), micro as one tenth (⅒), and nano as one twenty-fifth (1/25). We total the fractions across your estate and round down to the nearest whole number. That total is your billable projects. For example, a serverless monorepo with 247 detected projects might be just 49 billable projects.
How is a project's size — and its billing fraction — decided?
By three measured signals on every scan: source-file count, source byte size, and declared dependency count. A project lands in the lowest tier whose limits it meets on at least two of the three. Nano requires under 10 source files, under 1 MB of source, and under 5 dependencies; Micro requires under 20 source files, under 2.5 MB of source, and under 10 dependencies; Small requires under 30 source files, under 5 MB of source, and under 25 dependencies; anything larger is Standard. It's automatic — there is nothing to configure and no way to manually reclassify a project.
Does a big lockfile push my project into a higher billing tier?
No. Size is measured on source code only. Lockfiles (such as pnpm-lock.yaml, package-lock.json, yarn.lock, Cargo.lock, go.sum and poetry.lock), generated manifests, vendored dependency directories like node_modules, vendor, and CocoaPods Pods (and Carthage), and build output like dist or .next are all excluded from the file-count and byte-size signals. A single pnpm-lock.yaml can exceed 1 MB on its own, so excluding it is exactly why a one-file Lambda with a big lockfile is still correctly billed as nano.
My project grew into a bigger tier. Will my bill jump immediately?
No. A project's tier is re-evaluated on every scan, but billing changes are applied carefully so your bill never rises unexpectedly mid-month. If a project crosses up a tier, it keeps its cheaper rate for the rest of the current billing cycle and the higher rate takes effect from the next cycle — the pending change is flagged in advance in the dashboard as a pending upgrade. If a project shrinks, the cheaper rate applies immediately.
How is the billable project number rounded?
Always down to the nearest whole number — never to nearest, never up. We add up each project's fraction (standard ×1, small ×⅓, micro ×⅒, nano ×1/25) to get a raw total, then floor it. So 1.9 billable raw is billed as 1, and nine micro-projects (0.9 raw) cost nothing. Rounding down at the estate level is what lets a monorepo of tiny functions sit cheaply — or even free — under governance.
See a real scan run
A replay of the actual CLI running against our test repositories — live progress, real findings, a genuine DriftScore. Nothing executes in your browser.