Billing FAQ
Overview
KScope's billing model is designed for transparency, simplicity, and alignment with real usage. We charge based on the number of billable resources/assets ingested and contextualized through our Blueprints—our connector framework that integrates with operational sources like AWS, Azure, GitHub, and more.
For enterprise customers, specific terms outlined in your contract will take precedence over the general information provided here.
📘 Note: You can find the complete list of billable assets/resources for each integration in the corresponding Blueprint help documentation.
Billing Model: Asset-Based Pricing
KScope uses an asset-based billing model, where customers are billed based on the number of active, non-ephemeral assets/resources in their environment.
What qualifies as a billable asset/resource?
A billable asset/resource is any entity ingested by a Blueprint integration that is not system-generated or marked as transient/ephemeral. These can include cloud infrastructure elements, code repositories, users, policies, and more—depending on the data source.
For example:
In AWS: EC2 instances, S3 buckets, IAM users
In GitHub: Repositories, teams, pull requests
In Azure: Resource groups, VMs, service principals
Only actively tracked and contextualized entities count toward billing.
Frequently Asked Questions
Q: How is the number of billable assets calculated?
We take a daily point-in-time snapshot of the assets ingested by your Blueprints. System-created or ephemeral entities are excluded from the count. Billing is based on a rolling average of these daily counts over your billing period.
This ensures accuracy and smooths out spikes or short-lived changes in your environment.
Q: Can I control what assets are ingested and billed?
Absolutely. Each Blueprint offers fine-grained control over the asset types it ingests. You can configure which resources to include or exclude during integration setup. If a particular asset type isn’t valuable to your use case, you can disable its ingestion to avoid unnecessary billing.
Refer to the specific Blueprint’s help doc to see and manage the billable asset types available.
Q: Will short-lived or ephemeral assets affect my bill?
No. KScope’s billing system is designed to exclude transient or short-lived assets (like containers spun up during CI/CD pipelines). Our rolling average model ensures that brief spikes in asset count—daily or seasonal—don’t result in inflated charges.
Q: Where can I see the list of assets that affect billing?
Each Blueprint help page includes a detailed breakdown of which assets are ingested and counted toward billing. Review these pages regularly to ensure your integrations are aligned with your billing and compliance expectations.
If you have any questions about your current billing usage or want help optimizing your asset count, reach out to our support team at [[email protected]].
Last updated
Was this helpful?