Skip to content

DoiT Cloud Intelligence

Welcome to Customer Voice!

Have an idea? Share it. Your feedback directly shapes our roadmap.

Tell us the problem you’re facing and what your ideal solution looks like. The more specific you are, the faster we can act.

DoiT Cloud Intelligence

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

64 results found

  1. When creating a node, the amount of options might be overwhelming, especially if the customer doesn't know exactly their intent. If we add a search box that returns the actions for each box, it would help the customer discovery in cloudflow capabilities.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CloudFlow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Add a FinOps trigger/node responsible for configuring and enforcing budgets/limits for automations (Guardrail). This node should allow users to:

    Define budget thresholds (per project/account, tag, or flow)
    Set hard/soft limits for automated actions (e.g., stop, throttle, require approval)
    Trigger alerts or approvals when thresholds are reached or exceeded
    Expose configuration and status clearly in the UI and run history

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CloudFlow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Today we have real-time anomaly detection - rich with info, great to use and investigate, but get's dumped in to a shared slcak channel with 10s of people
    We tried building the cost alerts, did it with allocations we build in doit for each group, and sending by email to a dedicated slack channel. But we got a lot of false positives with it . we can only decide if it alerts on a % change or actual $ change. we only want to follow % change, but doing it without a min $ threshold to alerts just notified us…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. To support the proposed console integration of internal PSS support flow, we'd like the Console's Expert Inquiry to support the following:
    - recognise "visibility" attribute to determine if a product should be hidden from customer in the dropdown list
    - when a Doer is creating a new request under a customer tenant, a pop up dialog should be presented for the Doer to select whether the ticket will be private or viewable by the customer

    Please refer to the following requirement document for more details, including tags, assignee and UI mock-ups: https://doitintl.atlassian.net/wiki/spaces/fde/pages/1623883778/DoiT+Console+PSS+Internal+Request+Flow+Requirements

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    In Backlog  ·  0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Current behavior
    In Cloud Analytics reports, when using the filter or group-by control on resource ID, the selection dialog only lists up to 5000 distinct resource values. As a result, specific resource IDs that are visible in the report table (may not appear in the selection dialog and cannot be filtered or grouped on, even though they are present in the dataset.

    Impact
    This prevents customers from reliably drilling down to specific resources at scale, blocking important FinOps and DevOps optimization workflows. Customers are forced to export data to external tools to achieve the required level of granularity, which creates…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Customers with many AWS accounts need a fully programmatic way to complete the DoiT “Link account” + Kubernetes core enablement flow, especially during the EKS Intelligence → Kubernetes Intelligence migration. Today this must be done via the Console/CloudFormation flow and cannot be completed end‑to‑end via public APIs, creating manual work and coordination overhead for multi‑account orgs. The current Console flow relies on CloudFormation plus a backend webhook/validation step to register the role and mark features as enabled; this callback is not exposed publicly, so adding IAM permissions with Terraform alone doesn’t flip the feature state. As a result, there is…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  APIs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Currently, all admins bypass SSO completely, which is a security gap since those sensitive accounts are the ones we need to be secured the most. I understand the use case for having a breakglass account, but making all admins bypass it with no way to enforce it defeats the purpose of having SSO enabled to begin with.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Currently, when searching for an AWS account or GCP project, the result is just a static link to the asset details page. To check costs or settings, I have to click the result, wait for the page to load, and then navigate through menus again.

    Please make the search results more dynamic by adding "Quick Actions" directly in the dropdown. When I search for an asset ID, I would like to see buttons to:

    Open a Cost Report filtered specifically for that account.

    Go directly to the Cloud Flow or Attribution settings for that account.

    This would significantly reduce the…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Allow for invoices to have "Invoice period" column which you can sort by. When you reissue an invoice that information does not exist or gets lost. All invoices should have (mandatory, by law) an explicit period listed for which the invoice is charged.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add a button next to invoice to more easily raise an issue around that invoice.

    Should help with speeding up payments.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    • Get a daily/weekly email with a combined summary of changes since the prior week

    • Use the DoIt API to get a list of changes/history that is currently displayed in the UI

    • Get notifications of changes, such as a slack webhook that fires any time a new snapshot/change is created

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Is there any chance if we can test on the GCP Marketplace if we can offer DoiT's DCI offering as an all upfront payment?

    A customer would be very keen to do this and we have the contractual mechanism on this side.

    Some Google teams have suggested it wouldn't be possible but Sebastian based on what he could see, seemed to think it would be possible

    Per House BP:
    Assuming all upfront means annual payment, I see that it is possible to create a private offer for such. However our backend doesn't support annual, so some refinement and development would…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Due to previously planned work for the remainder of the year and into January, this work is slated for Q1 / early Q2 of 2026.

  12. Bigquery Lens should have reports going back more than 30 days. I believe at least 3 months would be sufficient to see usage changes and activity.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. We recently released the ability for Ava to be Cloud Diagrams aware, but in order to make this work you have to go back and forth between the CloudDiagrams UI and the DCI UI making the experience pretty clunky. This makes the barrier to entry pretty high to get value out of the feature.

    That being said, the output I got from the questions I asked was quite good and accurate. I asked what other services and resources are connected to a specific Lambda function.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Add domain-wide delegation to CloudFlow to enable Google Workspace customers to build with DoiT CloudFlows.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CloudFlow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Customer wants to be able to run a report and send the output data as a JSON to a user-specified API. They want to do this to track team costs in a third-party tool that their developers use.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. A customer would like the ability to create high level "Executive Diagrams" that does not show the same level of detail that is currently being showcased. Would like something to show leadership that visualizes that it is say a 3 tier web app and the relevant services.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Due to security scans and their results, customers may require to update the S3 policies for the S3 buckets that DoiT manages and uses for EKS Lens.

    Please review whether ths following policy can be implemented for all customers (attached)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. When the Snowflake Lens is first connected, there is nothing on the screen that would designate it's processing. Similar to AWS Lens, EKS Lens, Pulse, etc - it would be extremely helpful to provide visualization of some sort that billing data is getting ingested.

    Here's link showing the lack of information on end user's side: https://share.zight.com/rRuKk9ge

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Currently, customers using the Doit console to purchase Microsoft 365 subscriptions or licenses are limited to monthly billing. Annual subscriptions require direct engagement with our sales team. This necessitates the creation of annual contracts, often for a small number of licenses, which consumes significant time in managing Ironclad and Salesforce for minimal revenue.

    To improve efficiency, I propose enabling customers to purchase a limited number of Microsoft 365 licenses (e.g., fewer than 50) through our console with both monthly and annual billing options. This would significantly reduce the administrative overhead associated with low-volume annual contracts.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?