Through User details, you can manage items such as Name, Email, Role, Group, and Last Login.

Yes, you can modify the roles and groups for each user account.
The available roles are as follows:
Admin: Has access to all menus and can perform most tasks, including adding users and updating settings.
Manager: Oversees organizational resources and approves access/resource requests.
Developer: Monitors their own resources and submits resource requests.
Operator: Provides and manages resources requested by developers.

‍

IAM, short for Identity and Access Management, registers and manages user accounts and access information.

Click the 'New Group' button to add a group.
This allows you to link multiple users and resources into a single group, granting access permissions to specific data and virtual machines.
You can specify the Group Name, Description, and Members.

‍

It allows you to grant users access permissions to specific data and virtual machines.
By linking multiple users and resources into a single group, permissions can be easily managed.
Groups registration information is provided in a table format, where you can view Group Name, Members, Linked VM, Last Updates, and Creator.

‍

Click the 'Add Key' button to add a new 'API Key'.
You can specify the Provider (Proxmox, VMware, OpenStack), Host Address, Key Type (API Token, Client Credential), and Datacenter Name.

‍

It allows you to manage API keys for integration with external systems or services.
API key registration information is managed in a table format, where you can view Datacenter Name, Provider, Host Address, Key Type, and Status.

‍

Click the 'New Policies' button to add a new 'Alert Policy'.
You can specify the resource type, resource metric, trigger settings, cooldown period, and other parameters to create the alert policy.

‍

You can easily enable or disable alerts by simply clicking the toggle switch.

Alert Policies manage notification rules and alerts for system monitoring.
Configured alerts are processed in connection with Notifications.

‍

Yes, by clicking a node, you can view all information for the selected node.
You can see the status of nodes assigned to the cluster (Critical, Warning, Good), visualize the status of virtual machines on a map (Good: Green, Warning: Orange, Critical: Red, Stopped: Gray), view the operational status of all assigned VMs, check VM resource usage in scatter plots, and access detailed node information including Storage Status, System Log, and Node Task History.

‍

Yes, by clicking on a cluster, you can view all information for the selected cluster.
You can check cluster status (Critical, Warning, Good), virtual machine status (Running, Stopped, Paused, Unknown), resource usage by cluster (CPU, Memory, Storage), detailed node information (Provider, Uptime, Hosted VM, CPU Usage, Memory Usage), and cluster log information.

‍

Infrastructure resource information is provided in a tree format based on clusters, allowing you to check resource usage and optimization.
The tree is structured according to the cluster hierarchy and can be viewed in the order of 'Cluster' > 'Nodes'.

‍

'ITSM Requests' is a feature for managing cloud resources through a resource request and approval process, providing a list of ITSM request information.
(This feature will be developed in the future).

‍

Yes, by clicking the 'Go to Infrastructure' button in the incident details, you can access a link to the 'Infrastructure Tree', where you can view information about the nodes and VMs related to the incident.

It provides detailed incident information and analysis data in a table format.
You can view details such as incident type, threshold exceedance status, category, assignee, and report creator information.
(The Analytics tab will be developed in the future.)

‍

It monitors the incident status and resource status of the entire infrastructure.
You can view pie charts showing the status of Incidents (Resolved, In Progress, Open), Severity (Critical, Warning), Resource Type (VM, Node), and Metric Types (Memory Usage, CPU Usage, Network Out, Disk Read, and others).

‍

Yes, you can create a new VM by clicking the New VM button.
You can specify the VM Name, Authority Group (a group registered in Group Management), Provider (Proxmox, VMware, OpenStack), Node, Template selection, Compute (Socket, Core, Memory), OS, and Storage.

‍

VM status information is displayed in a table summarizing the virtual machines. It provides detailed information such as VM Status, Provider, Type, Instance ID, Node, CPU Usage, Memory Usage, Storage Usage, Uptime, Host Memory, Authority, and UUID.

Node status information includes Node Status, Node ID, Provider, Cluster, Uptime, Allocated CPU, Hosted VM, and detailed information on CPU, Memory, and Storage.

The status of running virtual machines (VMs) is provided in a scorecard format, allowing you to check compute resource utilization such as CPU usage, memory usage, and storage usage.

It monitors and manages the status of virtualization instances (compute resources).

Yes, in 'Infrastructure Overview', 'Resource Topology' is provided considering the structural characteristics of VMs.
Storage and Network connected to the VM are also displayed in a topology format, and you can check information related to specific storage or network failure detection.
The color indicators are the same as those used for VM status information.

‍

Yes, resource status is visualized with color indicators from the agent level to the alert level, allowing users to intuitively understand the status at a glance. This method is applied consistently across all OpsNow Prime features.
‍
Black: No Agent Installed
Blue: Agent Installed + No Alert Policy
Green: Agent + Alert Policy + No Alerts (Healthy)
Yellow: Warning Alerts Present
Red: Critical Alerts Present

‍

The infrastructure follows a hierarchical structure of Cluster - Node - VM.
This structure can be easily viewed through the 'Infrastructure Tree'.

You can monitor the status of all managed infrastructure resources including Node, VM, Storage, and Network.

Yes, you can view recent change activities through 'Recent Changes' in the 'Infrastructure Monitoring Dashboard'.

Yes, by clicking on a node mapped to a cluster, you can view detailed information about the selected node.
You can check the mapped cluster, node summary information, VM summary information, node metrics, alerts, and recent change history.

‍

Yes, in 'Infrastructure Top 10 Resource', you can view the Top 10 resources for CPU, Memory, Disk I/O, Network I/O, and Storage Usage.

You can view cluster information, nodes belonging to the cluster, VM summary information, resource usage, alerts, and recent change history.

On the 'Infrastructure Monitoring Dashboard' page, you can select an individual cluster under 'Cluster Availability' to view its detailed information.
In 'Cluster Availability', you can see charts showing CPU and memory resource usage for each operating cluster.

‍

It is a dashboard that provides real-time infrastructure resource monitoring and resource metrics in the form of visualized charts, allowing users to understand all information at a glance.

The service is provided through a contract-based agreement, either by direct inquiry or through a partner.
OpsNow Prime is not offered directly to end users of cloud services. Instead, it is a solution provided mainly to enterprises and public institutions through business contracts.
Accordingly, companies adopting OpsNow Prime will enter into a separate agreement to define the service scope, responsibilities, and support policies.

‍

[From the VMware Alternative Perspective]
It is a practical alternative for companies struggling with the rising cost of VMware. OpsNow Prime eliminates license cost burdens with its open-source foundation and provides an intuitive single interface to manage multi-cloud IaaS environments. With real-time monitoring, automated alerts, and RBAC-based resource control, it makes managing complex infrastructures simple and efficient.

[From the Multi-Cloud Integration Perspective]
Although 87% of enterprises operate multi-cloud environments, many face challenges due to a lack of visibility and operational complexity. OpsNow Prime, based on Proxmox, unifies heterogeneous IaaS environments into a single intuitive platform. With real-time resource monitoring, automated provisioning, and role-based access control, it reduces complexity while strengthening control.

The upcoming features of OpsNow Prime include the following:
1. Expanded support for OpenStack and VMware.
2. ITSM, resource request, approval systematization, and real-time workflow monitoring.
3. AI-based incident management automation.
4. Application of MCP (Multi Context Protocol) standard.
5. A2A (Agent to Agent) collaboration technology.
6. xPU (GPU/NPU/TPU) resource monitoring and visualization of estimated power costs.
7. PaaS (CI/CD automation and application management).
8. AI Agent as a Service (Hybrid cloud operation management using only natural language prompts).
   Natural language-based cloud management using AI Agents.
  * Cloud operation management with AI Agents using standardized MCP protocol.
  * Simplified complex cloud operations with natural language prompts (e.g., CI/CD build and deployment).
  * Automatic generation of natural language diagnostic reports and suggested solutions in case of incidents.

Ultimately, these features aim to support efficient and systematic cloud infrastructure operations.

‍

1. Proxmox-based Virtual Infrastructure Management
Provides virtualization infrastructure management and control based on Proxmox, offering cost reduction benefits through migration from VMware to Proxmox.

2. Real-time Incident Detection and Response
Enables real-time detection and management of incidents, supporting an optimized operational environment.

3. AI-Ready Multi-Cloud Platform
Lays the foundation for a next-generation multi-cloud platform designed for intelligent AI cloud management.

4. GPU Resource Monitoring (Scheduled for release in Q2 2026)
Includes GPU resource monitoring capabilities for AI/ML workloads and high-performance computing (HPC).

OpsNow Prime IaaS is an open-source virtualization platform based on Proxmox that provides integrated infrastructure management capabilities to simplify the complexity of heterogeneous multi-cloud infrastructure management. It also serves as the foundation for upcoming AI-based features.

OpsNow Prime IaaS v1.0 provides virtualized computing resources as infrastructure. Using this infrastructure, users can manage virtual machines, storage, networks, and operating systems.
- VMs provide computing resources, and users can create, manage, and adjust them.
- Resources can be scaled up or down as needed, allowing users to increase or decrease computing capacity based on their requirements.
- It supports various databases and development environments, allowing users to configure environments as needed.
- For automated management, APIs can be used to automate resource provisioning, monitoring, and security.

‍

It is an AI Hybrid CMP platform that integrates and manages various hybrid cloud environments and costs in a single platform.
In the OpsNow Prime target model, the following are managed:
- IaaS: Infrastructure resources such as VM, storage, network, and GPU
 (On-premises installation is the default, and private cloud deployment is also supported)
- PaaS: Database, container platform, middleware, CI/CD, etc.
- SaaS: Public cloud cost and usage status (current OpsNow product line)

In other words, OpsNow Prime integrates and manages all clouds including on-premises, private and public clouds, VM, container, and GPU.

‍

OpsNow collects and securely retains various types of personal and service usage data to provide cloud cost optimization, account management, user support, and security monitoring.
All data is processed based on user consent, legal compliance and global cloud security standards.

✅ Categories of Personal Data Collected

🟦 Basic Identification Information

• Email address (required)
• Full name
• Company and department
• Phone number
• Preferred language
• Billing information (credit card number, expiration date, etc.)

🟦 Support & Operational Data

• Email messages and tickets submitted to OpsNow support
• Technical support logs and attachments (e.g., screenshots, error logs)
• Organization profile and history of requests or configuration changes

🟦 Login & Authentication Information

• Login and logout timestamps
• IP address, browser, and device metadata
• Multi-factor authentication (MFA) logs and verification history

🟦 Service Usage Activity (Expanded Scope)

• Cloud resource usage records (from Usage menu)
  • Instance lists and status (running, stopped, terminated)
  • Region, instance type, OS, vCPU count, lifecycle type (on-demand, reserved, spot)
• Cost analytics logs (from Analytics menu)
  • Daily/monthly spend per account
  • Cost distribution breakdown
  • Custom analytics queries and tag-based filters
• Optimization logs (from Optimization menu)
  • Resource right-sizing (e.g., downsizing, modernization) suggestions and actions
• UI interaction data
  • Filter usage, date range selections, and dashboard behavior tracking

‍

✅ Security and Legal Compliance

OpsNow protects all collected personal information and service records through an encrypted storage and access-controlled security system.

Our data retention and deletion policies are strictly managed in accordance with domestic and international regulations, including the Personal Information Protection Act, the Electronic Financial Transactions Act, and the Protection of Communications Secrets Act.

‍
💡 You may request a data backup or early deletion within 6 months after account deactivation by contacting customer support or your organization admin.

OpsNow retains customer data based on customer type (paid, free, trial) and data category in compliance with global data security standards and relevant privacy laws, including GDPR and Korean data protection regulations.

✅ General service data (e.g., cost, asset, usage history)

• Paid customers: Data is stored for a minimum of 13 months, up to 3 years.
• Free/trial customers: Data is retained for up to 1 year starting from the trial activation date.

This includes cloud cost analysis, resource utilization logs, and optimization history.
‍

✅ Billing data (invoices, payment history)

• Regardless of customer type, billing records are retained until the account is deleted.
• After account deletion, data is either removed or anonymized according to OpsNow's internal policies.
  ‍

✅ Personal information

OpsNow may collect and retain the following personal data:

• Required fields: Email, full name, company name, phone number, preferred language, credit card info
• Metadata: Login IPs, browser info, service usage history
• Support data: Customer inquiries, tickets, and file attachments

🔒 These personal details are stored until account deactivation, and are then deleted within the following

‍

✅ What happens to data for trial users?

• For trial users who do not convert to a paid account, some data is deleted immediately.
• Remaining data is retained for a maximum of 3 months, except for metadata like company name/department, which may be stored for up to 6 months for backup purposes.
  ‍

✅ Can I request data backup or early deletion after leaving OpsNow?

• Yes. Within 6 months after account deletion, customers can request:
  • 🔄 A downloadable data backup file via email
  • 🗑️ Immediate early data deletion

Please contact OpsNow Customer Support (CS) or your workspace administrator to submit a request.

OpsNow is committed to protecting customer data through transparent retention and deletion practices that align with legal requirements and industry best practices.

‍

An Organization in OpsNow FinOps Plus is a dedicated space where cloud resources, cost data, and policy settings can be independently managed and monitored by specific teams or departments.
Each company account can create up to 10 organizations, and access to each organization is strictly permission-based—only authorized users can view or manage its cloud data.

Organizations are ideal for companies that need to:

• ✅ Separate cloud costs by team, business unit, or project
• ✅ Assign clear ownership and visibility across departments
• ✅ Monitor usage and spending without data overlap
• ✅ Maintain security while working with internal teams and external partners

With OpsNow, each organization can manage:

• 💰 Cloud cost trends and optimization opportunities
• 📊 Resource usage and performance indicators
• 🔐 Governance policies and compliance configurations

You can also assign users to different organizations with role-based access controls, helping you maintain data isolation, accountability, and operational efficiency across multi-cloud environments.

📌 If your company manages multiple teams or departments in the cloud, OpsNow Organizations help you build a scalable and secure FinOps model.

‍

Yes. OpsNow’s Policy Management fully supports Google Cloud Platform (GCP), in addition to AWS and Azure, allowing you to generate and manage GCP-specific policy compliance reports in the same way.

To enable Policy Reports for GCP, you’ll first need to configure IAM permissions and grant access to required resources. OpsNow provides clear setup guidance, including Terraform scripts, so you can easily complete the integration process.

Once permissions are in place, GCP accounts can be scanned automatically based on your selected compliance standards, just like in AWS or Azure. You’ll be able to:

• Generate compliance reports across GCP environments
• Identify and drill down into non-compliant resources
• Automatically schedule report delivery and manage historical logs

📌 With this integration, your organization can maintain consistent compliance monitoring across all major cloud platforms, eliminating the complexity of managing policies separately for each provider.
‍

✅ Summary:

• Fully supports policy reporting for GCP cloud accounts
• Requires initial IAM permission setup, with Terraform scripts available
• Offers the same features as AWS/Azure: scanning, reporting, alerts, and history
• Enables unified compliance governance in multi-cloud environments

‍

Yes. OpsNow’s Policy Management allows you to schedule policy reports to be delivered automatically on your preferred frequency—daily, weekly, or monthly—based on the needs of each team or stakeholder.

You can even assign different delivery schedules to different recipients. For instance, your security operations team might receive daily reports to respond to incidents quickly, while your executive or compliance teams might prefer weekly or monthly summaries for strategic oversight.

Report scheduling is easily configured through the Settings menu, and any changes you make take effect immediately for the next scheduled report.

📌 This flexibility helps your organization stay continuously informed about policy compliance, reduce manual tasks, and ensure that the right people receive the right information at the right time.
‍

✅ Summary:

• Set report delivery to daily, weekly, or monthly intervals
• Customize delivery frequency by recipient role (e.g., DevOps, Security, Audit)
• Adjust schedules easily through settings; changes apply instantly
• Improve compliance visibility and reporting automation across teams

‍

Yes. OpsNow’s Policy Management provides a real-time, visualized dashboard that shows your organization’s cloud policy compliance status at a glance.

In the Report tab, you can monitor the results of automated policy scans across AWS, Azure, and GCP accounts using intuitive graphs and tables. The dashboard presents:

• Compliance status by policy item (Compliant / Non-compliant / Unprocessed)
• Compliance rates by framework (e.g., GDPR, HIPAA, SOC2) displayed as percentages
• Clickable charts that lead to detailed views of non-compliant resources

This real-time visualization isn’t just for technical teams. It’s designed to be clear and actionable for security teams, managers, and executive stakeholders alike—making it easier to track organizational risk and respond quickly.

📌 Whether you're managing a multi-cloud infrastructure or preparing for an audit, OpsNow’s dashboard gives you centralized visibility into policy adherence across your entire environment.
‍

✅ Summary:

• Monitor real-time policy compliance visually via charts and tables
• View compliance status across all cloud accounts and standards
• Get a clear picture of organizational risk at a glance
• Designed for both technical and non-technical stakeholders

‍

Yes. With OpsNow’s Policy Management feature, you can freely assign policy report recipients—including internal team members, department leads, or external compliance auditors—directly from the Settings menu.

Relying on a single person to receive all compliance reports can lead to delayed responses or bottlenecks in your governance process. For better alignment, it’s critical to tailor the distribution of reports to specific roles or teams, such as DevOps, Security, or Compliance, and also involve third-party reviewers when needed.

Using the Settings interface, you can:

• Add or update email recipients for each policy report
• Create custom recipient groups based on accounts, policy types, or compliance standards
• Allow recipients to access reports via email without needing an OpsNow account
• Ensure immediate application of recipient changes to the next scheduled report

📌 This capability empowers organizations to decentralize compliance oversight, improve collaboration with external stakeholders, and ensure timely visibility into policy violations.
‍

✅ Summary:

• Add multiple internal and external recipients to policy reports
• Customize recipient lists by policy type, team, or account
• Reports are delivered via email—no login required
• Supports collaborative governance and audit preparedness

‍

Yes. OpsNow’s Policy Management feature automatically stores all previously generated policy reports, which can be easily reviewed in the History tab.

In cloud operations, having access to past compliance data is essential. Without a clear audit trail, it becomes difficult to investigate recurring issues, demonstrate regulatory adherence, or prepare for internal and external audits.

The History tab in OpsNow helps users:

• View the complete list of issued policy reports
• Filter reports by date range to find reports from a specific period
• Use keywords, compliance standards, or account names to locate specific reports quickly
• Download past reports in PDF format or drill down to view non-compliant items only

This allows teams to track compliance trends over time, measure the impact of policy changes, and prepare evidence for audits or security investigations.

📌 With this feature, OpsNow turns one-time compliance snapshots into a long-term compliance intelligence system, enabling proactive governance.
‍

✅ Summary:

• Automatically stores and displays the full history of policy reports
• Supports date-based and keyword-based filtering
• Allows PDF re-download and non-compliance-only viewing
• Ideal for audit preparation, compliance trend analysis, and issue tracking

‍

OpsNow's Policy Management feature provides a powerful “View Details” function that allows you to precisely identify which cloud resources have violated specific policies—and why.

In large or fast-growing cloud environments, manually tracking which resource violated which compliance rule can be time-consuming, error-prone, and often unclear. This becomes especially critical in multi-account or multi-team setups, where knowing who owns what and what needs to be fixed is essential.

Within each Policy Report, users can click the [>] “View Details” button next to any non-compliant policy item. This reveals a detailed breakdown of:

• The specific cloud resource in violation (e.g., resource name, ID)
• The violated policy rule (e.g., unencrypted S3 bucket, open security group)
• The associated cloud account and region
• The current compliance status (Compliant / Non-compliant / Unprocessed)

This isn’t just a list—it’s actionable insight. You’ll know exactly which resource to fix, why it’s non-compliant, and which account it belongs to, so your team can prioritize remediation efforts immediately.

📌 With this feature, OpsNow helps you move from vague compliance metrics to clear, resource-level instructions for real-world action.
‍

✅ Summary:

• Get full visibility into non-compliant resources per policy item
• Identify exact resource name, account, violation type, and current status
• Prioritize remediation by seeing who needs to fix what, and why
• Eliminate guesswork from compliance reporting and response workflows

‍

Yes. OpsNow's Policy Management feature allows you to apply the same set of security and compliance policies across multiple cloud accounts and manage them centrally.

As organizations scale their cloud environments—often operating across AWS, Azure, and GCP—maintaining policy consistency across accounts becomes increasingly challenging.
Disparate configurations can lead to compliance violations, security gaps, and misaligned governance, especially in large or decentralized teams.

With OpsNow, you can define a unified policy set and apply it consistently across all connected accounts. The system then scans each account based on the same standards (e.g., GDPR, SOC2, HIPAA, AWS Well-Architected), ensuring uniform evaluation.

All results are visible from a centralized compliance dashboard, making it easy for teams to monitor the entire organization’s policy adherence in one place.

📌 This is especially valuable for organizations operating in multi-account or multi-team environments where policy standardization and centralized visibility are essential for security and audit readiness.
‍

✅ Summary:

• Apply the same policy set to all AWS, Azure, and GCP accounts
• Monitor organization-wide policy compliance in a single dashboard
• Eliminate gaps or inconsistencies in policy implementation across teams
• Maintain strong and standardized governance in complex cloud environments

‍

Yes. With OpsNow's Policy Management feature, you can easily generate and export audit-ready compliance reports without the need for manual formatting or editing.

Preparing reports for internal governance reviews or external compliance audits can be a time-consuming and error-prone task—especially in organizations with multiple cloud accounts. It often requires gathering data across AWS, Azure, and GCP, manually verifying policy adherence, and formatting it into a formal document.

OpsNow automates this process by scanning your cloud infrastructure based on selected frameworks (such as GDPR, HIPAA, SOC2, or AWS Well-Architected) and compiling the results into a structured, downloadable PDF report.

The report includes:

• Compliance status by policy (Compliant / Non-compliant / Unprocessed)
• Resource-level details of violations
• Cloud account associations and overall compliance rate

These reports are ready to be shared directly with auditors or internal stakeholders—no additional formatting required.

📌 Whether you're preparing for an audit, presenting to leadership, or documenting internal controls, OpsNow helps you maintain compliance documentation effortlessly and accurately.
‍

✅ Summary:

• Generate policy compliance reports in PDF format with one click
• Reports are structured according to standard compliance frameworks
• Save time by avoiding manual report formatting or data compilation
• Use for external audits, internal reviews, or governance reporting

‍

In cloud environments, resources are constantly created, modified, or deleted—sometimes in ways that violate security or operational policies. If these policy violations are not detected and addressed promptly, they can lead to serious risks such as security breaches, compliance failures, or unnecessary costs.

OpsNow FinOps Plus offers an automated system through its Policy Management feature to help prevent such risks and ensure timely response when violations occur.

Policy reports are automatically generated on a daily, weekly, or monthly schedule, based on user-defined settings. These reports are delivered via email to designated recipients, such as DevOps teams, compliance managers, or security leads.

Each report includes a clear breakdown of compliance status by framework (e.g., GDPR, SOC2, HIPAA), along with detailed lists of non-compliant resources, violated policies, and affected cloud accounts. This ensures that teams can identify and remediate issues as soon as they arise.

For managers or auditors who may not have real-time dashboard access, scheduled email alerts serve as a reliable method for staying updated and maintaining policy oversight across AWS, Azure, and GCP environments.

✅ Summary:

• Receive automated policy violation alerts without relying on manual monitoring
• Get policy reports delivered to your inbox on a regular schedule
• Detect issues early and reduce response time to security and compliance risks
• Ensure audit readiness and prevent policy drift in complex multi-cloud infrastructures

‍

No, with OpsNow Policy Management, you no longer need to manually check the compliance status of each cloud account.
The feature automatically scans your entire multi-cloud environment (including AWS, Azure, and GCP) and generates compliance reports based on selected standards like GDPR, HIPAA, SOC2, and AWS Well-Architected.

Reports are visually organized to show which items are compliant, non-compliant, or unprocessed, allowing operations and security teams to quickly detect and respond to policy violations.

🔎 With this automation, you can eliminate repetitive manual checks and gain real-time visibility into cloud policy compliance status, reducing security and audit risks across your organization.

‍

Policy Management in OpsNow FinOps Plus automatically audits cloud environments—across AWS, Azure, and GCP—for compliance with security, operational, and governance policies, and generates actionable reports.

This feature helps organizations operating complex multi-cloud infrastructures to monitor policy violations proactively, reduce manual compliance checks, and streamline audit responses with automated, up-to-date reports.

✅ What problems does it solve?

• Difficulty managing and tracking policy compliance across multiple cloud accounts (AWS, Azure, GCP)
• Time-consuming manual checks for compliance status by cloud admins or security teams
• Risk of missing policy violations and exposing the organization to security threats
• Inefficiency in preparing compliance documentation for internal or external audits

🔧 Key capabilities

🔧 Key Capabilities of Policy Management

• Automated policy scanning & reporting
  Automatically scans cloud resources for compliance based on standards like GDPR, HIPAA, SOC2, and AWS Well-Architected Framework. Supports AWS, Azure, and GCP environments.
• Visual compliance dashboards
  Provides real-time dashboards showing policy compliance status. Instantly identifies which policies are compliant, non-compliant, or unprocessed.
• Scheduled report delivery
  Sends policy compliance reports automatically to designated recipients on a daily, weekly, or monthly schedule. Useful for internal reviews and audit readiness.
• Violation-level detail visibility
  Shows exactly which cloud resources, accounts, and policy rules are in violation. Helps prioritize remediation efforts with precision.
• Audit-ready history tracking
  Keeps a complete history of previously issued reports. Enables easy access, filtering, and comparison of past compliance results in the History tab.
• Multi-cloud compatibility
  Fully supports AWS, Azure, and GCP through simple integration, including support for subscription-level policy scans in Azure.

‍

👤 Who benefits from this feature?

• Security & compliance managers: Automate monitoring and get audit-ready reports across cloud platforms
• Cloud operations teams: Instantly identify and prioritize remediation for non-compliant resources
• Governance or internal audit teams: Secure traceable, downloadable reports for audit readiness

‍

If you no longer wish to use OpsNow, you can permanently delete your account directly through the [Profile] menu. Once deleted, all account-related data is permanently removed and cannot be recovered.

✅ Steps to delete your account:

1. Go to the [Profile] section from the left-hand navigation.
2. Scroll down to the Delete Account section at the bottom of the page.
3. Click the [Delete] button.
4. Carefully read the warning message and follow the on-screen confirmation steps to finalize the deletion.
   ‍

⚠️ Important notes:

• Once deleted, your account data, profile settings, and usage history cannot be recovered.
• Even if you sign up again using the same email address, your previous data will not be restored.
• If your account has admin or ownership privileges, you may need to transfer organization access or close the workspace before deletion is allowed.

‍

OpsNow offers Multi-Factor Authentication (MFA) to enhance account security by requiring a second layer of verification in addition to your password. Enabling MFA helps prevent unauthorized access and protects your account from identity theft.

✅ How to enable MFA in OpsNow:

1. Go to the [Profile] section from the left-side menu.
2. Scroll down to find the Multi-Factor Authentication section.
3. Click the [Enable] button.
4. Scan the displayed QR code using an authenticator app such as Google Authenticator or Microsoft Authenticator.
5. Enter the 6-digit one-time code (OTP) generated by the app to complete registration.

✅ What happens after activation:

• Every time you log in, you will be required to enter both your password and the MFA verification code.
• If we detect login attempts from new devices or suspicious locations, MFA will be triggered automatically.
• MFA is configured per user and can be enabled without admin intervention.

💡 For improved security, we recommend enabling MFA for all users in your organization.

‍

OpsNow allows users to change their display name (User Name) directly from the [Profile] menu. This name is used throughout the platform to identify you in dashboards, team views, and collaboration features.

To update your user name, follow these steps:

1. Go to the [Profile] section from the left-hand menu.
2. Enter the new name in the User Name input field.
3. Click the [Save] button to apply the changes.

Once updated, your new name will be reflected in:

• Internal team member lists and dashboards
• Areas where your account appears within the organization
• Collaboration views visible to Admins or other users

💡 Your user name is separate from your email address and can be updated anytime by the account owner. It helps personalize your OpsNow experience and improve clarity during collaboration.

‍

To configure SAML-based Single Sign-On (SSO) in OpsNow, you need to input certain SAML metadata values into your organization's Identity Provider (IdP) settings. These values are provided within the [Authentication] menu once SSO is enabled.

Here are the key values:

• ✅ Assertion Consumer Service (ACS) URL
  This is the endpoint where OpsNow receives authentication responses from your IdP.
  → Copy this value into the ACS URL field in your IdP configuration.
• ✅ Entity ID (Service Provider Entity ID)
  This uniquely identifies OpsNow as the service provider.
  → Paste this value into the Entity ID field in your IdP setup.

These values are auto-generated when you enable [SSO Login] in OpsNow and can be copied easily using the provided copy buttons.

💡 Tip: Share these values with your IdP administrator to streamline the SSO configuration process. Once configured, users can log in to OpsNow via your internal authentication system using the SSO login option.

‍

OpsNow supports SAML 2.0-based Single Sign-On (SSO), allowing seamless integration with your company’s Identity Provider (IdP) for secure and centralized user authentication.

To enable SSO, follow these steps:

1. Navigate to the [Authentication] menu.
2. Toggle the [Enable SSO Login] switch to ON.
3. Enter the following required SAML credentials:
   • Issuer URL (Entity ID): The unique identifier provided by your IdP
   • SAML 2.0 Endpoint (HTTP-POST): The IdP's authentication endpoint URL
   • X.509 Certificate: The public certificate used for signature validation
4. Click the [Save] button to apply the configuration.

Once enabled, users can sign in via the SSO login button on the OpsNow login page without entering individual usernames or passwords. All authentication is handled through your internal IdP system.

This setup enhances security, simplifies user access, and enables centralized identity management for your cloud environment.

‍

OpsNow provides a secure way to create and manage API keys that allow external systems or automation tools to access cloud resources.
You can perform all API key operations in the [API Key] menu by following these steps:

1. Click [Add New API Key] in the top right corner of the screen.
2. Enter a name for the key (e.g., monitoring-tool-key).
3. Click [Generate] to issue a unique API authentication key.

The full API key is displayed only once at the time of issuance, so be sure to copy and store it in a secure location.

Once created, you can manage your keys by:

• Activating or deactivating them
• Deleting keys that are no longer in use
• Viewing the creator and issued date of each key

API keys are especially useful for integrating with DevOps pipelines, third-party monitoring tools, or cost analysis systems that require secure, token-based access.

‍

OpsNow automatically tracks and stores organization-level changes to support auditability and security compliance.
You can view this information under [Security > Organization History], including:

• Changes to the organization name
• Addition or removal of members, and modifications to user permissions
• Who performed the change, when it occurred, and what was changed
• Type and purpose of each change (event details)

This feature is critical for maintaining a secure and transparent operational record within your cloud environment. It helps identify unauthorized actions, supports audits, and prevents misconfiguration or abuse of admin privileges.

All change logs are stored automatically in real time, and no manual setup is required to start tracking.

‍

Yes. OpsNow allows administrators and authorized users to track login and logout activity of all team members within the organization.
Go to [Security > Member Activity] to access the following details:

• Login and logout timestamps for each member
• IP addresses used during access
• Type of activity (LOGIN or LOGOUT)
• User email and identifier info

This feature is essential for organizational security audits, detecting unusual access, and maintaining cloud compliance. You can use it to:

• Check for abnormal logins by former employees or external users
• Detect suspicious access from unfamiliar time zones or locations
• Analyze login patterns to assess risk or improve security posture

Security teams can leverage this information for real-time monitoring and fast incident response.

‍

In OpsNow, users can easily track their personal login and logout activity through the security panel.
Go to [Security > My Activity] to view:

• Login and logout timestamps (chronologically ordered)
• The IP addresses used during access
• Activity type (LOGIN or LOGOUT)

This feature helps users verify that their account is being accessed from trusted locations only. If an unknown or suspicious IP address appears, it can prompt immediate security investigation or password reset.

For administrators, these logs are valuable for auditing login patterns, identifying compromised accounts, and ensuring cloud security compliance.

‍

What features does the Security menu offer?

The Security menu in OpsNow provides a centralized dashboard where users and administrators can monitor all security-related activity logs across accounts and organizations. It includes the following tabs:

• My Activity: View your personal login and logout history along with the IP address used. This helps detect any suspicious activity on your account.
• Member Activity: Check when and where other team members in your organization have logged in or out, with details such as email addresses and IP logs.
• Organization History: Track all organization-related changes, such as organization name updates, member additions or removals, and role or permission changes.

This functionality is especially useful for auditing, abnormal login detection, and organizational security management in cloud environments.

‍

AutoSavings is built with a strong focus on security and least-privilege access when connecting to your AWS environment. It requires minimal permissions to analyze your usage and optimize costs safely and efficiently.

✅ 1. Role-Based Delegated Access (via IAM)

• AutoSavings connects to your AWS account using a delegated IAM role, not by storing credentials.
• You create a trusted role ARN that allows OpsNow to securely access your environment via AWS STS.
  ‍

✅ 2. Required Permissions: Read-Only by Default

• In most cases, AutoSavings works with read-only permissions, such as ReadOnlyAccess, to collect:
  • Usage data for EC2, RDS, and other services
  • Billing and cost-related information
  • RI and SP commitment details
    ‍

✅ 3. Additional Permissions for Automation (Optional)

• To enable automated purchasing and reselling of commitments, additional permissions are required:
  • ec2:PurchaseReservedInstancesOffering
  • ec2:ModifyReservedInstances
  • ec2:SellReservedInstances

These are granted explicitly and transparently, and customers can review or revoke them at any time.
‍

✅ 4. Security Architecture

• AutoSavings uses AWS Secure Token Service (STS) for temporary session-based access, ensuring no sensitive credentials are stored.
• All user access within OpsNow is governed by Role-Based Access Control (RBAC), and only organization owners can manage AWS connections.

‍

AutoSavings currently supports Amazon Web Services (AWS) only.
It is purpose-built to optimize AWS cloud costs through the following capabilities:
‍

✅ Supported Features on AWS:

• Automated purchasing and management of Reserved Instances (RI)
• Optimization of Savings Plans (SP) based on real usage
• Reselling underutilized RIs via the AWS Marketplace
• Dynamic usage pattern analysis to recommend cost-saving commitments

AutoSavings is designed to maximize cost savings on AWS by leveraging commitment-based pricing models—ideal for organizations with underutilized resources or complex usage patterns.
‍

🔄 Future Support:

Support for other major cloud service providers such as Microsoft Azure and Google Cloud Platform (GCP) is on the roadmap and will be added in future updates.

‍

AutoSavings automatically reduces AWS cloud costs by analyzing your usage patterns and executing commitment-based optimization strategies—all without manual effort.

✅ Key cost-saving methods:

1. Optimized RI/SP Purchases
   • AutoSavings analyzes your cloud consumption and automatically purchases Reserved Instances (RI) and Savings Plans (SP) to replace expensive on-demand usage with lower rates.
     ‍
2. Reselling Unused Commitments
   • If any commitments are underutilized, AutoSavings resells them via the AWS RI Marketplace to minimize waste and recover value.
     ‍
3. Auto-Correction for Coverage Gaps
   • When coverage is insufficient, the system automatically adjusts by purchasing additional commitments, maintaining cost efficiency.
     ‍

With this automated approach, AutoSavings enables organizations to realize consistent cloud savings without needing to manage purchases, adjustments, or resales manually.

‍

Most cloud account connection issues in OpsNow FinOps Plus are caused by insufficient IAM permissions, missing API configurations, or incomplete setup steps.
Please check the following based on your cloud provider:

✅ For AWS:

• Make sure the CloudFormation stack was executed successfully.
• The user or role running the stack must have IAM role creation permissions.
• Confirm that the OpsNowStackRole or similar IAM role was created in your AWS account.
• Verify that the role includes at least ReadOnlyAccess or equivalent policies.
  ‍

✅ For Azure:

• The registered app in Azure must be assigned at least the Reader role.
• Ensure API permissions such as user_impersonation are granted in the App Registration.
• If the Client Secret is expired or invalid, generate a new one and update it in OpsNow.
  ‍

✅ For GCP:

• Check that Billing Export is linked to a BigQuery Dataset.
• The service account must have Editor or higher permissions on the dataset.
• Make sure the JSON key file is valid and current.
• Required APIs like Cloud Billing and BigQuery API must be enabled in your GCP project.

📌 These issues are typically related to cloud security configurations.
If the problem persists, please reattempt the connection using an admin-level account or contact your cloud security administrator.

‍

OpsNow FinOps Plus allows you to register and manage multiple cloud accounts across AWS, Azure, and GCP individually.
For AWS, you can conveniently register multiple linked accounts simultaneously by connecting a Management Account.

Once the Management Account is authorized, all associated Linked Accounts are automatically added, enabling efficient operations even in large-scale multi-account environments.

Azure and GCP accounts follow individual setup processes, but once registered, all accounts are visualized and managed through a unified dashboard, providing clear insights across your entire cloud infrastructure.

This setup helps teams and organizations standardize FinOps practices across multiple clouds and business units.

‍

To connect a Google Cloud Platform (GCP) account to OpsNow FinOps Plus, you need to follow a step-by-step process that enables cost and usage data collection via BigQuery. The required steps are:

1. Create a BigQuery Dataset
   Set up a new dataset in BigQuery where GCP billing data will be exported.
2. Enable Billing Export and Required APIs
   In the GCP Billing menu, configure billing export to BigQuery and activate the BigQuery API and Cloud Billing API.
3. Create a Service Account
   Generate a service account with the necessary permissions to access the billing data stored in BigQuery.
4. Generate and Download the JSON Key
   Create a private key in JSON format for the service account and store it securely.
5. Upload the JSON Key to OpsNow Console
   Go to the [Cloud Accounts > GCP] menu in the OpsNow console and upload the JSON key file to complete the integration.

Once completed, OpsNow will automatically retrieve GCP cost and usage data, enabling detailed FinOps analysis and optimization.

‍

To integrate your Azure account with OpsNow FinOps Plus, you need to prepare specific credentials obtained from the Azure Portal. These credentials allow OpsNow to securely access your usage and billing data.

‍

📍 Where to Find These in Azure Portal

• Go to App registrations to get the Client ID and Directory ID
• Create the Client Secret in Certificates & Secrets
• Check your Subscriptions to verify the correct account
• Get the Billing Account ID under Cost Management + Billing
• For EA or MCA, obtain your API Access Key from the appropriate billing scope

📌 Once all credentials are correctly registered in OpsNow, the system will begin automatic cost and usage data collection from Azure.

‍

OpsNow FinOps Plus provides a fully automated AWS account integration using a CloudFormation stack, eliminating the need for manual role or policy configuration.

✅ Step-by-step process:

1. Go to the [Cloud Accounts] menu and select the AWS tab
2. Choose either the Step-by-Step or Express registration method
3. Click "Launch CloudFormation Stack"
   → This opens the AWS Console in a new window
4. Complete the stack creation process in AWS
5. OpsNow will automatically detect the stack and complete the account registration
   ‍

✅ Key benefits:

• Automatically grants required IAM roles and policies
• No manual input or credential pasting required
• Ensures secure setup with least-privilege permissions

📌 All configuration is handled through a single CloudFormation execution, making the process fast, secure, and reliable.

‍

In OpsNow FinOps Plus, you can connect your AWS, Azure, or GCP account to enable automated usage tracking, cost analysis, and optimization insights. Follow these steps:

✅ Access:

• Go to [Setting] > [Cloud Accounts] from the left navigation.
• Choose the cloud provider you want to connect: AWS, Azure, or GCP.
  ‍

✅ Available Methods:

• Express: Quick setup in a single-page form
• Step by Step: Guided setup process with detailed instructions

‍

After registration, OpsNow will start collecting your cloud resource and cost data automatically for FinOps automation.

OpsNow FinOps Plus requires access to your AWS, Azure, or GCP account in order to collect and analyze your cloud billing and usage data. This connection is essential to enable automated cloud cost optimization and FinOps workflows.

By connecting your cloud account, you unlock the following benefits:

• ✅ Collect usage data by resource: Retrieve detailed usage metrics for compute instances, storage volumes, and network resources.
• ✅ Automatically gather billing data: Aggregate costs by service, tag, and account based on native cloud billing exports.
• ✅ Identify potential savings: Detect unused reserved instances, idle resources, and oversized configurations.
• ✅ Generate automated reports: Receive cost trends, anomaly detection alerts, and optimization insights based on your real-time data.

🔍 Connecting your cloud account is the first step toward adopting FinOps. Without it, OpsNow cannot provide the visibility or recommendations needed to control your cloud spending.

‍

Yes. OpsNow allows you to create custom roles that grant limited access to specific menus such as Billing, Resources, or User Management.

• Assign view-only or edit permissions for each menu based on the user's responsibilities
• Customize access controls to fit complex team structures or external collaborator roles
• Apply the principle of least privilege to minimize exposure and reduce operational risk

📌 This is especially useful for organizations that manage cloud operations across finance, security, and engineering teams, allowing each team to see and act only on what they need.

‍

How can I quickly set up different member configurations for each organization?

OpsNow allows you to assign users and roles during the organization creation process, enabling fast setup of team structures.
You can also import predefined role templates or duplicate existing group settings to apply access policies more efficiently.

• Invite users and assign roles at the time of organization setup
• Apply permissions to teams or departments in bulk with minimal effort
• Maintain security with role-based access and least privilege principles

📌 This feature is especially useful for managing multiple organizations or global teams, significantly reducing setup time while improving administrative efficiency and access control.

‍

In OpsNow FinOps Plus, when a team member leaves the company, changes roles, or an external partnership ends, you can remove their access to cloud data by deleting the user from the organization.
This is an essential step for maintaining security and access control.
‍

✅ How to remove a user from an organization:

1. Go to [Settings] > [Organization] from the main menu.
2. Select the organization you want to manage.
3. Click the [Members] tab at the top.
4. Find the user you want to remove, and click the ‘X’ icon next to their name.

🔒 Important notes when removing a user:

• Removing a user from an organization does not delete their OpsNow account.
• Once removed, the user loses all access to the organization's cloud data, cost information, and settings.
• If a user no longer belongs to any organization, they will only be able to access the [Settings] menu.
• To permanently delete or deactivate an account, a separate account management process is required (see related FAQ).

📌 This feature is especially important for:

• Offboarding employees
• Ending external partner access
• Restricting access after internal role changes

‍

In OpsNow FinOps Plus, inviting a user as an Owner or as a General User determines the level of control they have within the organization. This distinction ensures proper role-based access control and helps minimize security risks.

✅ Owner Invitation

• Grants full administrative rights over the organization, including:
  • Creating/deleting the organization
  • Connecting or disconnecting cloud accounts
  • Managing all user roles and permissions
• Only Owners can access sensitive features like billing, policy enforcement, and security settings
• Recommended for: Organization admins, security leads, FinOps managers
  ‍

✅ General Invitation

• Used to invite users with limited permissions, such as:
  • Read Only (view-only access)
  • Read & Write (with restricted operational scope)
• Role can be selected at the time of invitation and updated later
• Ideal for: Team members, external partners, project contributors
  ‍

🔐 Security Best Practices

• Assign Owner role only to users who need full control, such as cloud administrators or team leads
• Invite all other users with the minimum required role to avoid unnecessary access exposure

‍

OpsNow FinOps Plus supports multi-organization (Organization) architecture, allowing you to operate separate cloud environments within a single account while applying granular access controls per organization.
‍

✅ How Access Control Works in Multi-Organization Environments:

• Organization-Level Access Separation:
  Each organization can be linked to its own set of cloud accounts (AWS, Azure, GCP). Users only see and access data within the organization(s) they’re assigned to.
• Role Assignment per Organization:
  A single user can have different roles across organizations. For example, they can be an Admin in one organization and Read-Only in another.
• Operational Isolation & Security:
  Although users log in with one OpsNow account, data and permissions are completely separated by organization, reducing security risk and improving compliance.
• Customizable Role & Access Policies:
  Define access levels at a granular level — including menus, features, and resource types — to suit enterprise or managed service provider (MSP) use cases.
  ‍

📌 Best for:

• Enterprises operating separate cloud environments by subsidiary, team, or department
• Organizations needing strong access separation for compliance or operational clarity
• MSPs or holding companies managing multiple clients or entities under one OpsNow instance

‍

In OpsNow FinOps Plus, the User Group feature enables administrators to manage large numbers of accounts more efficiently by grouping users with similar roles or responsibilities. This greatly reduces repetitive tasks and ensures consistent access control.
‍

✅ Benefits of Using User Groups:

• Bulk Role and Permission Assignment:
  Assign the same role and access level to all members in a group — no need to configure each user individually.
• Organization-Level Grouping:
  Assign an entire group to a specific Organization for fast deployment across teams or business units.
• Consistent Security Policy Enforcement:
  Apply read-only access to some groups, admin access to others — ensuring clear separation of duties and compliance with internal policies.
• Streamlined Onboarding:
  When new users join, simply add them to the appropriate group to automatically apply the correct settings.
  ‍

📌 Ideal for:

• Large teams managing hundreds of user accounts
• Organizations needing standardized permission control across business units
• Admins looking to reduce manual work and human error in access configuration

‍

Yes. OpsNow FinOps Plus provides fine-grained access control to help you securely share cloud data with external collaborators while maintaining strict organizational boundaries.

✅ How to securely share with external users:

• Assign Read-Only Access:
  When inviting external users, you can assign them a Read-Only role, which limits their access to view-only permissions and prevents them from making changes to infrastructure settings.
• Limit Access to a Specific Organization:
  You can restrict users to a single Organization, ensuring they only see data relevant to their assigned project or department — not the entire cloud environment.
• Use Custom Roles:
  Create custom roles with tailored access permissions, such as granting access only to billing data or specific dashboards.
  ‍

🔐 Use Cases:

• Sharing cloud usage data with external consultants or vendors
• Allowing access only to a specific project’s resources
• Preventing unauthorized access to sensitive internal data by limiting user roles and scope

‍

In OpsNow FinOps Plus, you can securely invite new team members or external partners to your organization with just their email address.
📌 During the invitation process, you can assign a specific role and organization to ensure least-privilege access is granted.

✅ Steps to Invite a New User:

1. Go to [User Management] and click the ‘+ Invite’ button
2. Enter the email address of the user to be invited
3. Select the Organization the user will belong to
4. Assign the appropriate Role (e.g., Member, Admin, or custom role)
5. Click [Invite] to send an email invitation
   ‍

🛡️ Tips for Security and Access Control:

• When inviting external collaborators, assign Read-only roles to restrict access.
• Use the Owner invitation only for internal administrators with full privileges.
• You can manage access by separating permissions per organization, which is ideal for multi-team or multi-project operations.

‍

Yes. If you ignore the resource optimization recommendations provided by OpsNow FinOps Plus, your organization may face significant financial and operational risks in managing cloud infrastructure.

💸 1. Increased Cloud Cost Waste

• Over-Provisioned Resources: Continuing to run instances with higher specs than necessary can lead to missed opportunities to reduce cloud spend without compromising performance.
• Idle Resources Left Unused: When unused or underutilized resources are kept running, they generate ongoing, unnecessary costs that reduce overall cloud cost-efficiency.
  ‍

⚠️ 2. Operational Inefficiencies

• Low-Utilization Resources Accumulate: If underused resources remain in specific regions, accounts, or by tags, they can distort budget tracking and showback/chargeback processes, making cost accountability difficult.
• Unnecessary Commitments: As cloud spending gradually increases, you may feel pressured to renew Reserved Instances or Savings Plans that are not optimally aligned with actual usage.
  ‍

📌 Optimization is not just a report

The Resource Optimization menu in OpsNow FinOps Plus is more than just a cost report.
→ It is a proactive cost control tool, and
→ A key enabler of operational efficiency across multi-cloud environments.

By regularly reviewing and applying the recommendations, you can maximize ROI on your cloud investment.

‍

OpsNow FinOps Plus allows you to customize optimization analysis criteria based on your organization’s policies and cloud environment.
You can define thresholds for resource usage, analysis duration, and classification logic to generate tailored cost-saving insights.
‍

✅ Configurable Parameters

• Usage Thresholds
  • CPU, Memory, Disk I/O, Network I/O usage
  • Example: Average CPU usage under 5%, memory usage under 10%, etc.
• Analysis Duration
  • Choose from 7, 14, or 30 days
  • Longer periods provide more accurate and reliable recommendations
• Recommendation Criteria
  • Idle: Extremely low utilization over the selected period
  • Downsize: Over-provisioned resources that can be scaled down
  • Modernize: Eligible for replacement with newer, more cost-efficient instance types
• Cloud-Specific Customization
  • Separate optimization rules can be configured for AWS, Azure, and GCP
    ‍

⚙️ Where to Configure

You can modify these settings directly from the
Optimization > Settings menu inside the OpsNow FinOps Plus console.

‍

OpsNow FinOps Plus updates its resource optimization analysis once daily.It uses the latest usage data to evaluate cost-saving opportunities across AWS, Azure, and GCP.
‍

✅ Automated and On-Demand Analysis

• Automated Daily Analysis
  • Runs every 24 hours
  • Reflects the most recent performance data to update recommendations such as Idle, Downsize, and Modernize
• On-Demand Manual Execution
  • Users can trigger real-time optimization analysis at any time by clicking the "Analyze all CSPs" button on the console
  • Results are immediately updated, allowing teams to make timely decisions based on the latest cloud usage

📌 Pro Tip

In addition to daily automation, you can run manual analysis after major deployments, cost reviews, or infrastructure changes to ensure optimization recommendations are always relevant and accurate.

Yes. The optimization recommendations (Right Sizing) provided by OpsNow FinOps Plus are cost-saving suggestions and do not automatically apply changes to your cloud resources.

You will need to manually implement the recommendations using your cloud console or IaC tools.
‍

✅ How to apply optimization recommendations

• Manual execution required
  Example: t3.xlarge → t3.medium
  Suggested instance changes must be manually implemented via your cloud provider's console (AWS, Azure, GCP) or through IaC tools like Terraform, CloudFormation, or ARM templates.
• What OpsNow provides
  • Recommended instance types
  • Before/after cost comparisons
  • Estimated monthly savings
    → All necessary information is provided in a clear, tabular format to support manual execution.
    ‍

🔄 Upcoming automated workflow support

OpsNow will soon support workflow integration for automatic execution.
This will allow organizations to apply changes more efficiently while aligning with internal security policies and approval procedures.

‍

OpsNow FinOps Plus automatically calculates the estimated cost savings (Saving Potential) for each optimization recommendation.
This provides organizations with a clear, data-driven projection of how much monthly cost could be reduced by following the suggested changes.
‍

✅ How Cost Savings Are Calculated

1. Comparison Target
   • The currently running instance type
   • The recommended instance type by OpsNow (for Downsize or Modernize)
2. Pricing Basis
   • Based on the on-demand hourly pricing from each cloud provider (AWS, Azure, GCP)
   • Reserved Instances (RI) or Spot pricing are not used in savings calculations
3. Time Basis
   • Monthly usage is calculated as 730 hours (24 hours × 30.42 days)
   • Hourly price difference × 730 = estimated monthly savings
     ‍

💡 Example

📌 Notes

• Estimated savings are based on on-demand pricing, so actual billing amounts may differ depending on RI/SP plans, discounts, or custom agreements.
• This metric is intended to help identify potential optimization areas, but final decisions on implementation remain with the user.

OpsNow FinOps Plus allows you to customize optimization analysis settings based on your organization’s policies and workload characteristics.
This helps ensure that Right Sizing and Idle Resource detection reflect your actual operational needs, improving both accuracy and trust in recommendations.
‍

✅ Key Criteria You Can Configure

1. Analysis Period
   • Default: 14 to 30 days
   • Defines the timeframe used to calculate average resource utilization
   • Shorter periods allow for more responsive detection; longer periods capture usage trends
     ‍
2. Utilization Thresholds
   • Set percentage-based thresholds for CPU, Memory, Disk, and Network usage
   • Example: CPU below 10%, Memory below 15% = categorized as Idle
   • Different thresholds can be applied to each optimization type (Idle, Downsize, etc.)
     ‍
3. Idle Resource Conditions
   • Instances with consistently low usage over the defined period are flagged as Idle
   • Analysis can include average, maximum usage, and access frequency
     ‍

⚙️ How to Set Criteria

• Console Path:
  [Optimization] → [Settings] → [Rightsizing from Recommendation]
• Settings are applied independently by cloud provider (AWS, Azure, GCP)
• Once saved, updated conditions are immediately reflected in analysis results
  ‍

📌 Customizing these settings helps you reduce noise in recommendations and focus on high-impact cost-saving opportunities, making it a key enabler of effective FinOps practices.

‍

The Exclusion Tag feature in OpsNow FinOps Plus allows users to exclude specific resources from optimization analysis.
This ensures that critical infrastructure or sensitive assets are not mistakenly flagged for cost-saving actions, supporting safe and accurate optimization.

✅ When to Use Exclusion Tags

• Critical infrastructure that must not be altered
  • e.g., production databases or core application servers
• Resources restricted by internal security or compliance policies
• Resources explicitly marked by internal rules to be excluded
  • e.g., env=production, tier=core, keep=true
‍

🛠️ How It Works

• Users apply Key/Value tags to resources they want to exclude.
• Then, within OpsNow (Optimization > Settings), they can define these as Exclusion Tags.
• This logic is applied consistently across AWS, Azure, and GCP environments.
  ‍

📌 Exclusion Tags help improve the precision and trustworthiness of optimization analysis, ensuring that critical workloads remain stable while maximizing cost efficiency where appropriate.

‍

OpsNow FinOps Plus automatically identifies unused cloud resources that are no longer in active use or have lost their associations.
This helps prevent unnecessary cloud spending and supports proactive cost optimization.
‍

✅ Detection Criteria for Unused Resources

OpsNow evaluates resource-specific conditions across each cloud provider to determine unused status:

• EBS (AWS):
  • Detached volumes not associated with any EC2 instance
• Elastic IP (AWS):
  • Public IP addresses not currently assigned to any instance
• ELB (AWS):
  • Load balancers with no backend instances registered
• Azure Disk:
  • Disks attached to stopped or deallocated VMs
• GCP Persistent Disk:
  • Disks not mounted to any Compute Engine instance
    ‍

🔍 How Detection Works

• OpsNow regularly gathers resource metadata via cloud provider APIs.
• Resources that remain disconnected or unused for a defined period are flagged as Unused.
• Vendor-specific logic is automatically applied to ensure accurate classification across AWS, Azure, and GCP.
  ‍

📌 Unused resources are often a hidden source of cloud waste.
By leveraging OpsNow’s detection engine, organizations can quickly identify and remove redundant assets, even across complex multi-cloud environments.

‍

OpsNow FinOps Plus automatically recommends Modernize actions when an instance is running on an older generation and there is a newer, more cost-effective instance type available that offers the same or better performance.

This helps organizations reduce cloud costs without compromising workload stability.
‍

✅ Criteria for Modernize Recommendations

• The current instance belongs to an older generation (e.g., t2, m4, D2s_v3)
  ‍
• A newer generation instance exists that:
  • Offers equal or better performance
  • Has a lower hourly cost
    ‍
• Examples:
  • t2.micro → t3.micro
  • m4.large → m6a.large
  • D2s_v3 → D2as_v5

🔍 How It Works

• OpsNow automatically detects old-generation instance types across AWS, Azure, and GCP.
• If a more modern instance type with a better price-performance ratio is available, the system recommends Modernize.
• These rules are pre-configured based on vendor benchmarks and not customizable by the user.
  ‍

⚠️ Optimization Purpose

• Unlike Downsize, which reduces resource specs,
  Modernize focuses on replacing old-generation instances with newer ones at the same performance level but lower cost.
• Since cloud vendors frequently release new, optimized instance types,
  continuing to use outdated instances can lead to significant cost inefficiencies.

📌 Modernize is a key strategy for reducing infrastructure costs without altering performance, making it especially effective for long-running workloads and legacy environments.

‍

The Resource Optimization menu in OpsNow FinOps Plus identifies overprovisioned cloud resources and recommends downsizing to more cost-efficient instance types based on actual usage data.

This feature helps reduce unnecessary spending by detecting resources that are consistently underutilized relative to their specifications.
‍

✅ Downsize Analysis Criteria

• Average CPU utilization
• Memory usage rate
• Network I/O activity
• Analysis window: Typically between 14 to 30 days
  ‍

🔍 How Downsize Recommendations Work

• If the system determines that a resource can operate reliably on a smaller instance type based on recent usage metrics,
  it is classified as a Downsize candidate.
• Examples:
  • t3.xlarge → t3.medium,
  • m6a.2xlarge → m6a.large, etc.
• Vendor-specific logic is applied automatically for AWS, Azure, and GCP, considering the unique instance family structures and performance baselines of each cloud.
  ‍

⚙️ Customizable Thresholds

• Users can define Downsize conditions based on internal policies:
  • e.g., CPU < 10%, Memory < 20% average usage, etc.
• The evaluation period and threshold values are fully configurable in the Settings panel.
  ‍

📌 Downsize is a core strategy for cloud cost optimization, allowing organizations to maintain performance while reducing infrastructure costs.

‍

OpsNow FinOps Plus automatically detects underutilized or inactive cloud resources (Idle Resources) across multi-cloud environments.
This feature helps organizations eliminate unnecessary cloud spending by identifying resources that consistently show low usage over a defined period.

✅ Key Analysis Metrics

• Average CPU utilization
• Network I/O activity
• Disk I/O activity

If these metrics remain below the defined threshold continuously, the resource is flagged as idle and is recommended as a cost optimization target.
‍

⚙️ Default Analysis Conditions (Example)

• Analysis window: Default is the past 30 days
• Threshold example:
  • Average CPU utilization below 1%
  • Minimal or no Network/Disk activity
• Vendor-specific logic:
  • Detection criteria are automatically tailored to AWS, Azure, and GCP’s respective performance metric structures.
    ‍

🛠️ Customizable Settings

• Users can configure custom thresholds and analysis periods to match internal policies.
• Resources with specific tags (Key/Value) can be excluded from idle analysis, allowing operationally critical instances to be preserved.

📌 Idle resource detection is a proactive feature that helps prevent unnecessary costs,
while improving infrastructure efficiency and cloud governance.

‍

OpsNow FinOps Plus analyzes the utilization and operational status of cloud resources and classifies cost-saving opportunities into the following four optimization types:

✅ Optimization Categories

1. Idle
   • Resources with little or no usage over a specific time period
   • Identifies underused instances that can be removed to eliminate waste
2. Downsize
   • Overprovisioned resources that can operate effectively with lower specs
   • Recommends smaller instance types to reduce costs without sacrificing performance
3. Modernize
   • Older instance types that can be replaced with newer, more cost-efficient ones
   • Examples include recommendations such as t2 → t3 or m4 → m6g
4. Upsize (disabled by default)
   • Resources consistently running at high utilization
   • Suggests upgrading to higher-performance specs for stability and efficiency
     ‍

These recommendations are automatically generated based on performance metrics defined by each cloud vendor (AWS, Azure, GCP).
Users can also configure custom thresholds such as CPU below 10% for over 30 days, depending on organizational policy.
‍

📌 These optimization types help organizations eliminate waste,
while turning resource insights into actionable cost savings across multi-cloud environments.

‍

The Resource Optimization menu in OpsNow FinOps Plus automatically analyzes the utilization and sizing of major compute and storage resources across multi-cloud environments, helping identify cost-saving opportunities.

Below are the key supported resources by cloud provider:
‍

✅ Supported Cloud Resource Types

• AWS (Amazon Web Services)
  • EC2 Instances
  • RDS Databases
  • EBS Volumes
  • Elastic IPs (EIP)
  • Elastic Load Balancers (ELB)
• Microsoft Azure
  • Virtual Machines (VM)
  • Managed Disks
• Google Cloud Platform (GCP)
  • Compute Engine Virtual Machines
  • Persistent Disks
    ‍

These core infrastructure components often represent the bulk of cloud spending.
OpsNow helps detect inefficiencies such as overprovisioned resources, unused assets, and outdated instance types, and provides actionable optimization recommendations including Idle, Downsize, and Modernize suggestions.

📌 OpsNow analyzes a wide range of resources across AWS, Azure, and GCP, and provides optimization recommendations tailored to the characteristics of each cloud provider.

‍

OpsNow FinOps Plus – Resource Optimization is an automated optimization tool designed to reduce unnecessary cloud infrastructure costs.
Unlike simple resource listings, this menu delivers actionable savings insights by identifying inefficiencies and recommending concrete cost-saving actions.

✅ Key Feature Components

1. Right Sizing Recommendations
   • Classifies cloud resources into Idle, Downsize, Modernize, and Upsize categories based on CPU, memory, and network utilization
   • Provides clear recommendations on optimized instance types along with estimated monthly savings
2. Unused Resource Detection
   • Automatically identifies unattached or inactive resources such as EBS volumes, Disks, Elastic IPs, and Load Balancers
   • Helps declutter infrastructure and eliminate wasteful spending
3. Custom Savings Criteria Settings
   • Enables users to define their own thresholds for CPU, memory, and IOPS usage
   • Supports configuration of analysis windows (e.g., 14–30 days) for each cloud provider (AWS, Azure, GCP)
4. Exclusion Tag Management
   • Allows certain critical or intentionally overprovisioned resources to be excluded from analysis using tags
   • Maintains operational stability while focusing on cost-saving opportunities
     ‍

📊 Optimization Impact

• Identifies underutilized or overprovisioned resources to significantly reduce cloud expenses
• Offers data-driven recommendations for optimal infrastructure performance
• Enables team- or business unit-level resource breakdown using tags, accounts, and regions
  ‍

🎯 Ideal For

• Organizations facing rising cloud infrastructure costs
• Teams that lack visibility into inefficient or wasted resources
• Enterprises that need to allocate cloud budgets more accurately across departments
  ‍

📌 The Resource Optimization menu is more than just a reporting tool—
it’s a strategic platform for cost-saving execution and infrastructure governance.

‍

Yes,.
In the Resource Usage menu of OpsNow FinOps Plus, you can filter cloud resources based on their assigned Tag Key/Value pairs to isolate and analyze specific sets of assets — such as those tied to a particular team, project, or environment.

🏷️ Key Features of Tag-Based Filtering

✅ 1. Search by Tag Key/Value

• Examples: Environment=Prod, Team=FinOps, Owner=lee.hj
• Easily isolate cloud resources by business function, project ownership, or organizational structure

✅ 2. Combine with Account and Region Filters

• Tag filters can be combined with Account (AWS Account / Azure Subscription / GCP Project) and Region filters
• Example: View only EC2 instances in us-east-1 under a specific AWS account where Team=DevOps

✅ 3. Ideal for Large-Scale Environments

• In environments with hundreds or thousands of assets, tag-based filtering enables operational segmentation and accountability tracking (showback) across departments or teams
  ‍

📌 Benefits of Using Tags for Resource Management

• Gain visibility into team- or project-specific cloud spending
• Enable internal chargeback/showback models with accurate resource grouping
• Simplify asset discovery in complex multi-account environments

‍

OpsNow FinOps Plus provides users with access to up to 13 months of historical cloud resource usage data by default.
This includes changes in resource status, specifications, and instance count — all available in daily or monthly views for precise trend analysis.
‍

📊 Key features of usage history tracking

• 13-Month Data Retention (Standard)
  → Monitor instance status changes (running, stopped, deallocated), resizing history, and lifecycle events
• Daily and Monthly Time Views
  → Flexible granularity for analyzing short-term spikes or long-term patterns in resource consumption
• Graphical Trend Charts in History Tab
  → Visualize changes in usage or instance specs across time directly on the UI
  ‍

💼 Extended History for Enterprise Plans

• Enterprise plan customers may receive unlimited access to historical usage data depending on their contract terms.
• This is especially useful for:
  • Long-term budget forecasting
  • Strategic FinOps planning and governance
  • Internal reporting and auditing documentation

📝 Note: Retention policies may vary depending on plan type or customization options. Long-term data access can be configured upon request.
‍

📌 Summary
OpsNow provides powerful tools for tracking cloud resource usage history over time, helping organizations detect trends, reduce waste, and support cost optimization strategies with long-term data.

‍

The Resource Usage menu in OpsNow FinOps Plus enables users to filter and explore cloud resources across AWS, Microsoft Azure, and Google Cloud Platform (GCP) using multiple dimensions.
These filters help improve operational visibility, support cost optimization, and allow for precise resource tracking across complex cloud environments.
‍

🔍 Key Filtering Criteria

1️⃣ Account / Subscription / Project

• Filter by cloud account level:
  • AWS Account, Azure Subscription, GCP Project
• Helps identify and manage assets across multiple business units or subsidiaries
  ‍

2️⃣ Region

• Filter by resource location (e.g., us-east-1, korea-central, asia-northeast1)
• Useful for spotting resource concentration or high-cost regional allocations
  ‍

3️⃣ Service / Product Type

• Filter by resource type: EC2, VM, Disk, Load Balancer, Cloud Function, etc.
• Enables side-by-side comparison of similar services across different CSPs
  ‍

4️⃣ Tags

• Use key-value metadata tags to group resources by team, department, owner, or environment
• Examples: owner=kim.jh, project=marketing, env=prod
‍

🧩 Advanced Multi-Filter Combinations

• Combine filters across all criteria:
  Account + Region + Resource Type + Tag
• Example: "Show only stopped EC2 instances in us-west-2 tagged with project=devops under Account A"

These filters apply not only to the Current view but also to the History tab, allowing users to analyze usage trends over time.
‍

📌 Summary
OpsNow’s powerful filtering capabilities allow users to narrow down cloud resources with precision and speed.
This makes it easier to identify idle, overprovisioned, or underutilized assets, and take timely actions for optimization and governance.

‍

The Resource Usage menu in OpsNow FinOps Plus provides a vendor-specific overview of resource data across AWS, Microsoft Azure, and Google Cloud Platform (GCP).
Users can monitor key attributes such as instance specifications, usage status, network details, tags, and billing type — helping identify overprovisioned or idle resources at scale.

✅ Key data fields available

• Resource Type: EC2, VM, Disk, Cloud Function, BigQuery, etc.
• Status: running, stopped, deallocated, terminated
• Specifications: vCPU, memory, OS, instance type, VM size
• Networking: Public/Private IP, Region, Availability Zone
• Operational Info: Launch time, lifecycle, billing type (On-Demand, Reserved, Spot)
• Tag Info: Name, Owner, Project, environment tags
  ‍

✅ Examples of supported resources by cloud

• AWS: EC2, EBS, RDS, AMI, NAT Gateway, Elastic IP
• Azure: Virtual Machines, Disk, Load Balancer, Network Interface
• GCP: Compute Engine VM, Cloud Functions, BigQuery, Firewall
  ‍

⚙️ Key Functional Benefits

• Status-based summary charts: Visualize the number of running, stopped, or deallocated instances
• Distribution insights: Identify resource concentration by type or region
• History view: Analyze changes in instance status and size over time with daily graphs
• Optimization integration: Surface recommendations like “Downsize” or “Modernize” to quickly spot cost-saving opportunities
  ‍

❓ How frequently is resource data collected?

OpsNow automatically collects resource usage and metadata from each cloud provider using their official APIs, ensuring up-to-date visibility.
‍

⏱ Standard Collection Interval

• Data is typically refreshed every 30 minutes to 1 hour for all connected accounts.
  ‍

⏳ Exceptions for new regions or types

When new regions or resource types are introduced, data collection may be delayed based on provider-side availability:

‍

This ensures that organizations have near real-time access to resource data, which supports optimization efforts, idle instance detection, and operational accountability.

The Resource Usage menu in OpsNow FinOps Plus enables organizations to view detailed resource data for AWS, Microsoft Azure, and Google Cloud Platform (GCP) environments.
It provides a vendor-specific interface where users can easily analyze the status, specifications, network details, and tagging information of cloud assets to optimize resource usage and reduce costs.
‍

✅ Resource Attributes Available for Analysis

Each resource entry includes key metadata such as:

• Resource Type: EC2, VM, Disk, Cloud Function, BigQuery, etc.
• Instance Status: running, stopped, deallocated, terminated, etc.
• Specification Info: Number of vCPUs, Memory, OS, VM Size, Instance Type
• Network Info: Public/Private IP, Availability Zone, Region
• Operational Info: Launch Time, Lifecycle, Pricing Model (On-Demand, Reserved, Spot)
• Tag Info: Name, Owner, Project — based on custom user-defined tags
  ‍

✅ Key Resource Types by Cloud Provider

🔹 AWS

• EC2, EBS, RDS, AMI, NAT Gateway, Elastic IP
• Also includes Key Pair, Tag Info, IP Addresses, and Availability Zone

🔹 Azure

• Virtual Machines, Disk, Load Balancer, Network Interface
• Displays details such as Subscription, Resource Group, VM Size, OS, Status, Region

🔹 GCP

• Compute Engine VM, Cloud Function, BigQuery Table, Firewall
• Includes Project ID, Resource ID, CPU Platform, OS, and Status
  ‍

⚙️ Functional Advantages

• Visualized Status Aggregation
  Instantly see the number of running, stopped, and deallocated instances through intuitive charts.
• Type/Region Distribution Charts
  Identify uneven resource allocation and usage concentration by type or region.
• Usage History Tab
  Analyze usage trends and instance status changes over time with daily historical graphs.
• Optimization Integration
  Gain automatic recommendations such as “Downsize” or “Modernize” directly on each instance to drive cloud cost savings.
  ‍

The Resource Usage menu is more than a static inventory; it provides actionable insight into cloud resource optimization and supports proactive FinOps decision-making.

‍

OpsNow FinOps Plus enables structured resource management using tag-based filtering, allowing you to organize and monitor cloud resources by department, team, project, or individual owner.
This tagging system is essential for effective cost allocation, accountability, and operational control.
‍

✅ Classify and filter resources using custom tags

• Resources can be filtered by common tag keys such as Department, Project, Owner, or Environment
• Examples: project:marketing, owner:kim.jh, env:prod
• This allows teams to isolate and manage only the resources relevant to their operational scope
  ‍

✅ Tag-based management enables cost and compliance control

Using tag-based views, organizations can:

• Allocate costs by department or project (e.g., chargeback or showback models)
• Track ownership and responsibility for each resource
• Identify security-sensitive environments, such as production or staging clusters, for targeted audits
  ‍

📌 Summary
OpsNow provides a powerful tagging framework that aligns cloud resource management with your organizational structure, enabling clear cost visibility, operational accountability, and governance at scale.

‍