Kubecost Alternitives RFI FY26.xlsx
XLSX spreadsheet 28 KB Posted
- Solicitation number
- A056967
About this file
This document is a Request for Information (RFI) for Kubecost alternatives, issued by the Department of the Air Force Materiel Command Lifecycle Management Center Joint Base San Antonio. The RFI seeks detailed information from potential vendors about alternative software solutions for Kubernetes cost management and optimization, with specific technical requirements including an HTTP-accessible API, comprehensive resource cost tracking, GPU usage monitoring, and cloud cost visibility across AWS.
Key requirements include providing a tenant-view of resources, supporting resource aggregation and filtering, offering reporting and alerting capabilities, enabling Single Sign-On authentication, and supporting deployment in secure, air-gapped environments across multiple impact levels. The RFI requests vendors to provide details on alternative license types, pricing information, transition and training costs, contract flexibility, and additional features. Vendors are expected to demonstrate how their solutions meet the comprehensive technical specifications for Kubernetes cost management, with a focus on functionality, scalability, security, and operational efficiency.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFI Excel version of Word sheet
| Alternative License Types: | |
| 1 | What alternate licensing models or solutions do you offer for [CURRENT SOFTWARE NAME]? |
(Please provide details on available options, such as enterprise, cloud-managed, or open-source/community editions. For each licensing option/solution set, please provide how it differs from the listed license.)
2 For each licensing option/solution set, please provide how it is similar from the listed license.
(Specify any feature restrictions, scalability limitations, or support differences among the licenses (e.g., data retention, search query limits, or alerting capabilities)
3 For each licensing option/solution set, please provide how it meets the above requirements.
(Identify core features or capabilities that are shared across all options, such as log aggregation, visualization tools, and monitoring capabilities, regardless of the license type.)
4 For each licensing option/solution set, clarify how it meets the above requirements for our logging and monitoring needs.
(Please highlight specific ways in which each licensing tier can address our operational, security, and compliance needs, particularly in areas like multi-environment visibility, role-based access control, and support for compliance auditing.)
| Pricing Information: | |
| 1 | For each license, please provide estimated transition and training costs and schedule for both transitioning to and from your proposed solution. |
(Include details on onboarding costs, consulting, or configuration support required for a smooth transition. Specify any training options available, such as workshops, online courses, or documentation resources, and their associated costs.)
2 For each license, please provide any price plans associated such as monthly, trial, annual.
(Indicate if discounts are offered for longer-term contracts or high-volume deployments. For cloud-managed options, provide cost breakdowns for storage, query processing, and other usage-based charges.)
| Other Considerations: | |
| 1 | Are there any additional features or benefits associated with the different licenses that we should consider? |
For example, are advanced analytics, machine learning-based anomaly detection, or pre-built integrations with other monitoring tools included at higher licensing tiers? - Clarify any value-added services, such as dedicated account support, proactive health checks, or best-practice workshops, that come with certain licenses.
2 Is your company willing to enter into contracts with a base year with up to four one-year options? If not, how many years is your company willing to agree to?
(For longer-term contracts, specify any guarantees on pricing, renewal terms, or opportunities to adjust the contract scope to accommodate potential changes in our data volume or monitoring requirements.)
Requirements Capability Sheet
| [Current License Name] ALTERNATIVE: | Kubecost | ||||
| Instructions: | Please select Y/N | Please select Y if Yes, N if no plans, or N/A if ready on day 1 | Please insert # of days from award to build capability or a date if known | Please insert comments, questions, or concerns for each requirement if needed | Could you please provide information on the following: |
What other soft ware solutions do you off er that can provide the requirements listed? For each solution listed, please provide the following information:
1.Alternative License Types:
-A capability summary or list that at a minimum addresses the requirements listed.
-How the capabilities diff er from Kubecost.
-How the capabilities are similar to Kubecost.
-Please provide a list of systems/soft ware that the license is currentlycompatible with and if there are plans to expand that list.
2.Pricing Information:
-What are the estimated transition costs associated with thesealternative licenses for both transition from Kubecost andtransitioning from the proposed alternative solution?
-What are the estimated training costs for the soft ware?
-Are there maintenance costs associated with the solution?
-Are the licenses priced in trial (weekly/short term), monthly,quarterly, and/or annual? If so, please provide the pricing plans andany links to existing contracts or your website.
-Is your company willing to enter into longer term contracts toinclude options for up to 4 subsequent years? Can those subsequentyears be priced or is there a parent Government contract that willcontrol that price?
-Please provide any existing Government contracts your companyhas on either DoD ESI or NASA SEWP.
3.FeatureComparison: -Are there any additional features or benefits associated with thediff erent licenses that we should consider? (This may includecapability PDFs, website links that describe the firewall, andcustomer/reference information.)
| Requirement: | Ready on Day 1 | Future Capability | Estimated date of Capability | Comments | |
| Example: | Please enter a Yes or No requirement that a possible alternative software vendor MUST meet. | Y | 8 | This Column is meant for the vendor to have space to answer the questions in more detail. | |
| 1 | The solution must off er an HTTP-accessible API that delivers comprehensivedata on Kubernetes resource costs and usage. This includes detailed informationon namespace costing, CPU, cloud memory, and other resource metrics. | ||||
| 2 | the API must provide cost and usage data for GPUs utilized in AI/MLworkloads. It should also off er visibility into all cloud costs across the customer’saccount(s) that are not associated with Kubernetes, ensuring compatibility withAmazon Web Services (AWS). | ||||
| 3 | The latency between actual usage and thereported data through this solution must not exceed 24 hours. | ||||
| 4 | the solution must include features for recommending optimal pod,container, and node sizes. It should identify unused resources and off er costforecasting based on current usage trends. | ||||
| 5 | A critical aspect is the ability toprovide a ‘tenant-ed view’ of resources, allowing for resource management andaccess control via groups, which can be applied through labels. | ||||
| 6 | The solution must support the aggregation of resources based on specific filters,facilitating a unified view of both Kubernetes and non-Kubernetes costs. | ||||
| 7 | Have the capability to manage shared resources at the Kuberneteslevel, enabling users to designate shared namespaces and allocate costsaccordingly. Users need to be able to organize and filter costs using a dashboard,with labels that are searchable. | ||||
| 8 | Reporting capabilities are essential, with the solution providing options tocreate and export reports in CSV and PDF formats. | ||||
| 9 | Alerting features must beincluded, allowing notifications through various chat software channels such asSlack or Mattermost. | ||||
| 10 | the solution should support Single Sign-On(SSO) using OIDC or SAML for user authentication. | ||||
| 11 | For highly secure environments, the solution must be deployable in fully air-gapped settings across Impact Levels 2, 4, 5, and 6. | ||||
| 12 | It should be available as a Stand-Alone deployment model,supporting on-premises cost management and optimization. | ||||
| 13 | Integration withcloud billing systems is crucial, enabling actions to optimize usage and apply any negotiated discounts manually. | ||||
| 14 | The solution must accurately handle variouspricing models, including spot (preemptive) nodes, reserved instances, andsavings plans. |
Leave Blank
| Y | Y |
| N | N |
| N/A |
File details come from the government source that posted it. Updated .