Member

Comprehensive documentation to help you get started with OpsNow

Need More Help?

More Questions?

For more information about OpsNow, visit our knowledge base

Contact Support

Our team is here to help with any questions you may have!

Member
Organization
Cloud Accounts
Billing
Security
Setting
Support

What is an Organization in OpsNow?

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.

How do I delete my OpsNow account?

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.

How do I change my user name?

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.

Can I create a restricted role that allows access to only specific menus?

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?

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.

How can I deactivate or remove a user from an organization in OpsNow?

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

What's the difference between inviting an Owner and a General User in OpsNow?

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

Our company operates multiple cloud environments by organization. How can we manage user access separately?

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

What are the benefits of using user groups for more efficient management?

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

Can I securely share sensitive data within the organization with external users?

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

What is the process for inviting a new user to the organization?

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.

How are user permission types distinguished in OpsNow?

OpsNow FinOps Plus defines user permissions across three roles: Owner, Admin, and Member. Each role determines what a user can see or manage within an organization.

✅ Owner

  • Has the highest level of access across the entire organization
  • Can perform the following:
    • Invite, delete, and assign roles to users
    • Create and manage organizations
    • Register and remove cloud accounts
    • View and update billing and payment settings
  • Best suited for enterprise administrators or cloud ops leads

✅ Admin

  • Has limited management rights within the assigned organization
  • Can:
    • Manage users within the same organization
    • Register and view cloud accounts
    • Access cost, resource, and optimization insights
  • Ideal for team leads or technical managers

✅ Member

  • Has read-only access to cloud cost and resource data
  • Cannot invite users or change account settings
  • Suitable for general users, analysts, or external stakeholders needing visibility only

Is there a limit on the number of users I can invite in OpsNow?

No, there is no limit to the number of users you can invite to your organization in OpsNow FinOps Plus.
You can freely add internal team members, departments, or external partners to collaborate within your cloud environment.

Each user is assigned a role-based access level (RBAC) at the time of invitation, including:

  • ✅ Owner – Full organization control
  • ✅ Admin – Manage users and cloud accounts
  • ✅ Member – View-only access to cost and resource data

This structure allows you to safely manage a large number of users while maintaining clear access control and governance.

📌 OpsNow is designed to scale with your team—whether you're managing a small startup or a large enterprise with cross-functional cloud teams.

Can I create multiple organizations under one company account?

Yes. In OpsNow, a single company account can create up to 10 organizations, each acting as an independent workspace for managing cloud cost analysis, resource usage monitoring, and governance policies.

This feature is ideal for enterprises managing multiple departments or regional teams, as it enables you to separate cloud visibility and control by organizational unit.
Each organization allows you to assign user permissions independently, helping you enforce access control and limit visibility to only relevant data.

✅ Use this feature to optimize multi-team operations, improve cost governance, and maintain security across your cloud environments.

Can I delete an organization?

Yes, OpsNow FinOps Plus allows you to delete organizations that are no longer in use. To delete an organization, go to [Settings > Organizations], select the organization you want to delete, and click [Delete Organization] at the bottom of the detail page.

🧩 Important reminders before deleting an organization:

  • Cloud accounts will be removed: All AWS, Azure, and GCP cloud accounts linked to the organization will be permanently deleted.
  • All collected data will be lost: Cost data, resource usage history, and optimization records associated with the organization will be permanently erased.
  • Irreversible action: Once deleted, the data cannot be recovered. We recommend backing up important reports or exporting data in advance.
  • User access will be revoked: All user roles and permissions associated with the organization will be removed.

💡 When should you delete an organization?

  • After project completion, department restructuring, or organizational changes
  • When rebuilding your cloud account structure and cost segmentation
  • When the maximum number of organizations (10 per company) is reached, and you need to free up space

✅ Deleting unused organizations regularly helps maintain cost visibility, improve security, and optimize cloud management structure in complex environments.

What is the difference between deactivating and removing a user account in OpsNow?

In OpsNow FinOps Plus, when a user no longer requires access—due to offboarding, contract changes, or inactivity—you can either deactivate or remove their account.
While both methods serve to protect your organization’s data, they differ in terms of how the account is handled.

✅ Deactivate: Temporarily restrict access

  • The user account remains in the system, but all service access is blocked.
  • The account can be reactivated later, preserving access history and organizational ties.
  • Best for:
    • Long-term absences (e.g., leave of absence)
    • Temporary suspension of partners or external vendors
    • Internal security audits

❌ Remove: Permanently delete the account

  • The account is completely removed from OpsNow.
  • The user loses all access and must be reinvited to join again if needed.
  • Best for:
    • Offboarded employees
    • Terminated vendor or partner accounts
    • Irrecoverable security concerns

📌 Summary Table

Action Deactivate Remove
Account Exists ✅ Yes ❌ No (permanently deleted)
Access Allowed ❌ No ❌ No
Reuse Later ✅ Possible (reactivate anytime) ❌ Not possible (must re-register)
Use Case Leave of absence, temporary suspension Termination, offboarding, contract ended

📌 Regularly deactivating or removing unused accounts helps prevent unauthorized access and strengthens your organization’s overall security posture.

No items found.

Can I export commitment reports to Excel or CSV format?

Yes, OpsNow FinOps Plus’s My Commitments feature allows you to export all commitment-related data as Excel (.xlsx) or CSV files for detailed reporting, internal collaboration, or external audits.

🔍 Key data included in the export

  • Commitment details (type, service, account, region, start/end date)
  • Current utilization rate
  • Commitment coverage
  • Estimated savings and ROI
  • Underutilization risk indicators
  • Recommended purchase options and savings forecasts

💡 Practical use cases

  • Submitting monthly commitment utilization reports
  • Sharing usage insights with finance or cloud operations teams
  • Supporting strategic commitment planning and budget allocation
  • Providing documentation for financial or compliance audits

📌 You can export data exactly as filtered and sorted on the screen.
Each tab — Recommendations, Coverage, Utilization, and Inventory — supports independent data export.

Can I identify areas with high On-Demand usage and find opportunities to switch to commitment plans?

OpsNow FinOps Plus offers a powerful feature within the My Commitments menu that identifies services or accounts with high On-Demand usage and provides data-driven recommendations on how switching to commitment plans (e.g., Savings Plans, Reserved Instances) could reduce your cloud spending.

🔍 What insights are provided?

  • Breakdown of On-Demand usage by service and account
    • e.g., EC2, RDS, Aurora, GCP Cloud SQL, Azure VM
  • Current On-Demand spend per resource
  • Estimated cost savings and ROI if converted to a commitment plan
  • Recommended commitment types (1-Year vs. 3-Year, No Upfront vs. All Upfront)

💡 How does this help?

  • Enables strategic decision-making for timing and scale of commitment purchases
  • Helps finance teams evaluate ROI and optimize budgets
  • Supports operations teams in reducing unnecessary On-Demand costs
  • Can be used alongside AutoSavings to enhance optimization coverage

📌 This feature is especially valuable when On-Demand costs are steadily rising.

It clearly answers:
“How much could we save right now by switching to a commitment?”

How can I identify if a cloud service or account is over- or under-committed?

The Coverage tab in OpsNow FinOps Plus – My Commitments provides a clear visualization of commitment coverage across services, accounts, and instance types. This helps organizations detect misaligned commitments and take action before waste or penalties occur.

✅ Identify Over-Provisioned Commitments

  • If a specific account or service shows a coverage rate over 100%, it means the committed usage exceeds actual consumption.
  • This may lead to unused commitments and potential financial waste.

✅ Identify Under-Covered Usage

  • If a workload is running entirely on On-Demand without any applied commitments (e.g., Savings Plans or RIs), the organization is missing out on available discounts.
  • These areas represent cost optimization opportunities.

✅ Visual Dashboard

  • The Coverage tab displays commitment vs. usage using bar charts and percentages.
  • You can instantly see the coverage rate for each service, account, or instance family, including:
    • Total committed cost
    • Actual covered usage
    • On-Demand spending

💬 Example:

“In the Asia Pacific (Seoul) region, the Aurora MySQL service shows 125% commitment coverage, indicating over-provisioning, while EC2 t3.medium instances are still billed as On-Demand, highlighting a gap in coverage.”

Benefits

  • ✅ Reduce waste from underutilized commitments
  • ✅ Convert On-Demand spend into discounted usage
  • ✅ Enable strategic commitment planning by account and service

Can OpsNow recommend when and how much commitment I should purchase?

Yes. OpsNow FinOps Plus’s My Commitments > Recommendations tab helps organizations optimize cloud costs by recommending the ideal timing and amount of additional commitment purchases (e.g., Savings Plans or Reserved Instances). These insights are particularly helpful for financial and cloud operations teams looking to improve cost efficiency.

All recommendations are generated by OpsNow Insight AI, which analyzes:

  • ✅ Historical cloud spend and usage trends over the past 3 months
  • ✅ Current commitment utilization and coverage gaps
  • ✅ Forecasted savings potential based on additional commitment simulation

Each recommendation includes detailed quantitative metrics such as:

Metric Description
Estimated Monthly Savings The cost savings achievable by purchasing additional commitments
Coverage Rate Increase The improvement in cost coverage (reduction in on-demand spend)
Return on Investment (ROI) Projected efficiency of the commitment (e.g., ROI 4.5x)
Optimal Commitment Structure Suggested term (1yr vs 3yr), payment type (All Upfront, No Upfront, Partial)

💬 Example AI-generated suggestion:

“Based on your average usage over the last 3 months, an additional $1,000/month in commitments is expected to yield approximately 12% in monthly savings (ROI 4.5x, +8% coverage improvement).”

🔍 These insights enable organizations to make data-driven decisions on cloud commitment purchases, ensuring maximum cost savings and resource efficiency. Thanks to OpsNow Insight AI, users can confidently plan and justify long-term commitment strategies with clearly measurable outcomes.

Can I receive alerts before my cloud commitment expires?

OpsNow FinOps Plus – My Commitments provides proactive monitoring of commitment expiration dates (e.g., Reserved Instances, Savings Plans). The platform automatically flags commitments that are set to expire within 30 days and delivers email alerts to help teams take timely action.

This feature is especially useful for preventing situations where key commitments expire without renewal, causing cloud resources to fall back to costly On-Demand pricing.

🔍 Key Features

  1. Automatic detection and highlighting of expiring commitments (30 days in advance)
    • In the Inventory tab, any commitment nearing expiration is flagged visually with clear indicators.
  2. Scheduled email notifications
    • Notifications are sent to designated recipients, ensuring that finance or DevOps teams are aware of upcoming expirations and can prepare for renewals.
  3. Actionable recommendations
    • Expiring commitments are accompanied by renewal or AutoSavings suggestions, enabling fast decision-making and preventing budget leakage.

✅ Benefits

  • Avoid losing long-term savings due to missed renewals
  • Improve visibility and control over commitment lifecycles
  • Enhance budget forecasting and cloud cost predictability

How can I identify underutilized commitments that are at risk of non-compliance?

The My Commitments feature in OpsNow FinOps Plus automatically detects cloud commitments that are not being fully utilized and flags them as Underutilization Risk. This feature is especially effective in identifying commitments that may incur penalties due to underuse, enabling teams to take early action and avoid unnecessary costs.

🔍 Detailed Features

  1. Real-Time Monitoring of Commitment Utilization Rate
    • Tracks usage amounts, unused amounts, and remaining contract periods per commitment.
    • Flags any commitment that is not being consumed at the expected pace as Underutilization Risk.
  2. Automatic Detection of High-Risk Items
    • When usage is low relative to the committed amount or when usage trends indicate it won’t be fully used by the end of the term, the system automatically warns you.
    • Example: A 3-year Reserved Instance is purchased, but less than 20% has been utilized.
  3. AI-Powered Predictive Analytics
    • OpsNow Insight AI analyzes historical usage patterns and resource trend changes to proactively detect commitments that are at increased risk of underuse in the future.
  4. Early Warning and Action Guidance
    • When an Underutilization Risk is detected, OpsNow provides in-depth insights along with strategic recommendations such as redesigning usage plans or switching to AutoSavings.

✅ Expected Benefits

  • Avoid penalties due to non-compliance with committed usage
  • Minimize waste and optimize commitment planning
  • Improve collaboration between cloud operations and finance teams (e.g., accelerate decisions on resizing or reassigning resources)

How can I find the best commitment purchase option for our organization?

The Recommendations tab in OpsNow FinOps Plus > My Commitments helps organizations identify the most cost-effective AWS commitment options—such as Savings Plans and Reserved Instances—based on actual cloud usage patterns. These recommendations are powered by OpsNow Insight AI, which performs advanced analysis to deliver personalized suggestions with high accuracy.

🔍 Key Benefits of AI-Based Commitment Recommendations

  1. Data-Driven Simulation
    • OpsNow Insight AI analyzes current usage by instance type, region, platform, and runtime behavior to simulate the most cost-efficient commitment scenarios across 1-year and 3-year terms, and various payment types (No Upfront, Partial Upfront, All Upfront).
  2. Transparent Metrics for Comparison
    • Each recommendation includes quantitative metrics:
      • Estimated Monthly Savings (e.g., $984.95/month)
      • Expected Coverage Rate (e.g., 94.84%)
      • Savings Rate, ROI projections, and side-by-side comparison of term/payment options
    • This empowers finance and DevOps teams to make decisions based on clear, objective data.
  3. Balanced Cost vs. Flexibility
    • For teams with budget constraints, options like No Upfront or Partial Upfront are highlighted.
    • For teams aiming to maximize ROI, 3-year All Upfront plans with the highest savings are recommended.
  4. Audit-Friendly Recommendation Engine
    • Each AI-based suggestion includes detailed justifications, making it easier to use in internal budget reviews, financial reports, or procurement workflows.

✅ Business Value

  • Avoid overcommitting or underutilizing cloud discount plans
  • Maximize long-term cloud cost savings through accurate, scenario-based projections
  • Strengthen internal transparency and trust through AI-driven, traceable recommendations

How can I check if my cloud commitments are being effectively utilized?

📌 OpsNow FinOps Plus offers a My Commitments dashboard that helps you track the real-time utilization of your cloud savings commitments such as Reserved Instances (RIs) or Savings Plans across AWS, Azure, and GCP.

Through this feature, you can view key indicators for each active commitment:

  • ✅ Amount used vs. committed
  • ✅ Remaining unused amount or percentage
  • ✅ Utilization rate over time
  • ✅ Forecasted consumption pace vs. remaining days
  • ✅ Inclusion of on-demand usage in the commitment

If any commitment shows a low utilization rate (e.g., below 50%), you’ll receive a Below Threshold Alert warning you of potential waste or underutilization.

💡 This allows you to identify and address inefficient commitments in advance, align your usage with your contracts, and improve your overall cloud cost efficiency.

What is the purpose of the My Commitments feature?

My Commitments is a unified management feature in OpsNow FinOps Plus that helps organizations maximize the value of their cloud commitments—such as Savings Plans, Reserved Instances (RIs), and Committed Use Discounts (CUDs)—while minimizing waste.

It solves key challenges faced by cloud finance and operations teams:

✅ What problems does it solve?

  • "We’re not sure if our existing commitments are being fully utilized."
    → My Commitments provides real-time tracking of usage rates, savings amounts, and utilization ratios to identify underused or wasted commitments.
  • "We don’t know when or what kind of new commitment to purchase."
    → The Recommendations tab analyzes current usage patterns and suggests optimal commitment options (e.g., 1-year vs. 3-year, no upfront vs. partial upfront).
  • "We’re spending too much on On-Demand because coverage is low."
    → The Coverage tab visually highlights how much of your cloud usage is covered by existing commitments vs. On-Demand spend, helping identify savings opportunities.
  • "We missed a commitment renewal and incurred unexpected costs."
    → The Inventory tab displays start/end dates and remaining terms for each commitment, so you can plan renewals or trigger AutoSavings in time.

🔍 Key Features Summary

Feature Description
Utilization Analyze usage rate, savings amount, and cost efficiency for each commitment
Coverage Visualize coverage ratio across all usage and detect On-Demand overages
Recommendations Receive intelligent suggestions for new commitments based on real-time usage
Inventory View all commitment details including type, term, scope, and payment structure

📌 My Commitments supports AWS, Azure, and GCP, and helps organizations take control of their commitment strategy—ensuring efficient usage, timely renewals, and data-driven optimization.

Service access is restricted due to non-payment. How can I check the invoice?

If your OpsNow FinOps Plus subscription has been temporarily suspended due to non-payment or billing failure, access to platform features may be limited.
However, invoice and billing information can still be accessed through authorized users.

✅ How to check the invoice:

  • Regular users cannot access invoices directly.
    To view the invoice, a request must be made to a user with Owner privileges—who has access to the [Billing] menu.
  • The Owner can go to [Billing > Billing Contacts] and register the email address of the person requesting invoice access.
  • Once added, even non-OpsNow users (e.g., finance team or external partners) will receive invoice notifications by email and can view the invoice without needing a login.

📌 OpsNow supports a flexible billing contact system so that invoices can be securely shared with external stakeholders—even when access to the service is restricted due to payment issues.

How can I delete a registered payment card?

In OpsNow FinOps Plus, you can delete a registered credit card from the [Billing > Payment Methods] menu.
However, if the card is currently being used for an active subscription (e.g., AutoSavings or Standard Plan), deletion will be restricted.

✅ When deletion is restricted:

  • The card is linked to an active subscription
  • Deleting the card without replacing it may cause payment failure or service disruption

🔄 Steps to safely delete a card:

  1. Go to [Billing > Payment Methods] and locate the card you want to delete
  2. Check if the card is currently used for any active service
  3. Take one of the following actions first:
    • ✅ Switch to another payment method for that service
    • ✅ Cancel the associated subscription
  4. Once the card is no longer in use, click Delete to remove it safely

📌 To safely delete a registered payment card, make sure to either update the payment method for any linked services, or cancel the related subscription before proceeding.

How can I change my payment card?

he method for changing your payment card in OpsNow FinOps Plus depends on your region.

✅ For customers in the US region
Go to [Billing > Payment Method], add a new card, and click [Set Default] to make it the default payment method.
You can also delete the old card using the [Remove] button.
Note: If the card is currently used for an active subscription, such as AutoSavings, you must switch to a new card first before removing the existing one.
→ Card information is securely processed and stored via Stripe.

✅ For customers in the Korea region
Card changes are not available through the system due to StepPay integration.
📩 Please contact [Customer Support] to request a card update.
→ Identity and business validation may be required during the process.

How is payment processed?

OpsNow FinOps Plus offers different billing methods depending on the customer’s region and subscription plan. Below are the details by plan type:

✅ Standard Plan

  • For customers in the U.S. region
    Payments are automatically processed via Stripe, using the credit card information provided at the time of subscription.
    Stripe is a widely trusted global payment gateway used by leading SaaS providers.
  • For customers in the South Korea region
    Payments are processed automatically via StepPay, based on the registered credit card.
    StepPay supports KRW billing, electronic tax invoices, and is optimized for Korea’s payment environment.

✅ Premium / Enterprise Plan

  • Applies globally to all regions
    For Premium and Enterprise plans, bank transfer (wire transfer) is the default payment method.
    OpsNow issues a tax invoice or formal billing invoice, and the billing frequency (monthly, quarterly) and payment terms (e.g., Net 15, Net 30) are defined during the contract process.

This invoicing model is ideal for enterprise-scale organizations and is commonly used in B2B SaaS agreements worldwide.

📌 For requests related to invoice details, billing frequency changes, or upgrading your plan, please visit the [Settings > Billing] menu or contact our support team.

My payment failed or is delayed.

If the payment fails, it is necessary to check whether the registered card has not expired.

Please verify the card information in [Billing > Payment Method]. If you update to valid payment card information, the payment will be retried within 1 day.

If there is a payment delay of more than 30 days after invoice issuance, AutoSavings service usage will be suspended.

In case of unpaid invoices for up to 3 months from the invoice date, the subscription will be canceled.

Can I use the service for free?

Yes, OpsNow FinOps Plus offers a free trial during promotional periods, allowing first-time users to explore the platform without submitting payment information.

During the trial period, you can access the following core FinOps features without limitations:

✅ Free Trial Features Include:

  • Multi-cloud cost analytics and visualization (AWS, Azure, GCP)
  • Resource usage monitoring and optimization recommendations
  • Budget management, cost anomaly detection, and governance reporting
  • Actionable insights to improve cloud cost efficiency

📌 Please note that the free trial is only available during specific promotional events.
Once the trial ends, you can continue using the service by selecting an appropriate paid subscription plan.

If the free trial promotion has ended, you can still contact our Customer Support to request a personalized demo.
Our team will guide you through the platform and show you how OpsNow can optimize your cloud operations and reduce costs.

What types of personal data does OpsNow collect and retain?

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.

How long does OpsNow retain customer data?

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

Data Category Deletion Timeline
Account registration details Within 3 months of deletion
Payment & billing records Within 5 years
Customer support history Within 3 years
Access logs (login activity) Within 3 months

✅ 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.

How do I enable Multi-Factor Authentication (2FA/MFA)?

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.

Where can I find the information required to set up SSO?

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.

How do I configure SSO (Single Sign-On) in OpsNow?

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.

Where can I generate and manage an API key?

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.

Where is the organization change history stored?

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.

Can I view the login history of team members?

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.

Where can I check my login history?

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?

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.

If I delete a connected cloud account, will its data also be deleted?

No. In OpsNow, deleting a connected cloud account does not immediately delete the data that was previously collected from that account.

✅ What happens to the data?

  • Once a cloud account is removed, any historical data such as cost records, usage logs, and optimization history associated with that account will still be retained.
  • This data will remain in your workspace until your OpsNow account is fully deleted, after which it will be automatically deleted according to the platform’s data retention policy.

✅ What changes after the account is deleted?

  • After you delete a cloud account, OpsNow will no longer collect or analyze new data from that account.
  • All real-time cost analysis, resource usage tracking, and optimization recommendations will be discontinued for that account.
  • Historical data remains read-only and cannot be updated.

💡 For example, if you remove an AWS account, you can still view the past 6 months of usage and cost data, but no new billing data, usage metrics, or budget alerts will be generated from that account going forward.

How do I set up two-factor authentication?

You can set up two-factor authentication (2FA) through the 2FA setup button in the [Settings > Profile] menu.

What is the session timeout criteria?

Session Timeout: Active sessions may expire after a maximum of 1 day.

How do I change my password?

You can change the Edit button in the Password section of the [Settings > Profile] menu.

How can I resolve permission errors when connecting a cloud account to OpsNow?

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.

Can I register multiple cloud accounts at once?

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.

How do I connect a GCP account to OpsNow?

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.

How do I connect my Azure account to OpsNow?

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.

Item Description
Application (Client) ID Unique ID generated from App registration
Directory (Tenant) ID Tenant identifier from Azure Active Directory
Client Secret Value Secret key for app authentication (from Certificates & Secrets)
Billing Account ID Identifier for your Azure billing account
API Access Key Key for programmatic access to billing data (varies by account type)

📍 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.

How do I connect an AWS account to OpsNow?

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.

Where can I register a cloud account in OpsNow?

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
Cloud Provider Required Setup
AWS Run CloudFormation stack for permission delegation
Azure Register app and provide API credentials
GCP Set up BigQuery project and upload service account key (JSON)

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

Why do I need to connect my Cloud Account to OpsNow?

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.

The process of registering AWS, Azure, and GCP Cloud Accounts is difficult. Can I get help with account registration?

Please register the StepBy Guide Viewer Chrome Extension to provide the OpsNow Guide. Detailed instructional balloons are provided for each step of the cloud account registration process, making it easy to complete the registration.

[Install StepBy Guide Viewer Chrome Extension]

How do I change permissions?

You can change permissions in the [Settings > Members] menu or [Settings > Organizations] menu.

The [Members] menu may not be visible depending on the user's permissions, and users can only change permissions for users with the same or lower permissions.

You can change Owner to Admin or Member in the [Members] menu. When changing permissions, you need to set the organization and permissions.

You can change Admin or Member to Owner in the [Members] menu. When permissions are changed, the owner has all permissions for organizations and billing.

You can change Member to Admin or Admin to Member in the [Members] and [Organizations] menus. When changing permissions, different permissions can be granted or changed depending on the organization the user belongs to.

How do users withdraw or leave?

If a user wishes to withdraw voluntarily, they can do so by using the 'Delete Account' function in the [Settings > Profile] menu.

How do I create an organization?

Organizations can be created through the 'Add' button in [Settings > Organizations]. When creating an organization, you need to input the name for the organization.

Can the same user be in multiple organizations?

Yes. You can invite users to the desired organization in the [Settings > Organizations] menu. Users can be granted different permissions for each invited organization.

Owners have permissions for all organizations, so separate organization settings are not possible for them.

Can I register the same cloud account in multiple organizations?

No. In OpsNow FinOps Plus, a single cloud account—such as an AWS account, Azure subscription, or GCP project—can only be registered to one organization at a time.

This restriction exists to ensure data integrity, security, and proper governance across all environments.

✅ Why duplicate registration is not allowed:

  • Consistent and accurate data
    Duplicate registrations may result in duplicated usage or cost data, skewing analytics and reports. OpsNow maintains a 1:1 relationship between cloud accounts and organizations to prevent this.
  • Clear responsibility and permission control
    Cloud accounts are typically managed by specific departments or teams. Multiple registrations can cause conflicts in user roles, ownership, and permissions.
  • Security and policy enforcement
    Since each organization in OpsNow can apply its own budgets, alerts, and governance policies, multiple registrations can lead to policy conflicts or compliance risks.

📌 If multiple teams need access to a shared cloud account, consider:

  • Structuring them under one organization with separate teams or projects
  • Inviting users from different groups to a single organization with appropriate roles, instead of duplicating the account across organizations

How long does it take to confirm data after registering an account?

Data collection will be completed in approximately 24 hours at maximum.

You can check the registered accounts and data collection status in the [Overview] menu.

What permissions are applied when registering an AWS account, and how are they managed?

When registering an AWS account in OpsNow FinOps Plus, permissions are automatically provisioned using an AWS CloudFormation stack.
This ensures that only the minimum required privileges are granted, based on the principle of least privilege, to support functions such as cost analysis, resource monitoring, and tag-based management.

✅ CloudFormation-Based Role Setup

Once the CloudFormation stack is launched from OpsNow, it automatically creates and configures:

  • A secure CrossAccountRole that allows OpsNow to access your AWS account
  • A predefined set of IAM policies tailored to cost, usage, and resource visibility
  • External ID and AssumeRole conditions to enhance cross-account security

📂 Key Permissions Included

  • Cost & usage tracking: ce:Get*, cur:DescribeReportDefinitions, s3:GetObject
  • Resource monitoring: ec2:Describe*, cloudwatch:ListMetrics, autoscaling:Describe*
  • Tag-based analysis: tag:GetResources, tag:GetTagValues
  • Read-only IAM access: iam:List*, iam:Get* (for visibility only, not modification)

📌 These permissions are read-only and strictly scoped, with no execution or deletion capabilities.

🔍 How to verify and manage permissions

  • After registration, you can review all permission settings in the [Settings > Cloud Accounts] menu
  • You may also audit and modify the role and policy details in the AWS IAM console at any time
  • If needed, OpsNow supports custom role scoping to meet your organization’s internal security policies

📌 Using CloudFormation for automated IAM role provisioning reduces configuration errors, ensures consistency, and enforces secure and transparent access for cloud cost and usage monitoring.

I want to opt-out of marketing communications.

If you toggle off the marketing consent switch in [Settings > Profile], you will opt-out of receiving marketing communications.

What are the security and account permission requirements for using AutoSavings?

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.

Which cloud environments does AutoSavings support?

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.

Does AutoSavings monitor costs in real time?

Yes. AutoSavings continuously collects and analyzes the most up-to-date cloud usage and cost data.
It automatically tracks your AWS consumption patterns in near real-time, enabling accurate and timely savings recommendations without manual effort. This ensures maximum visibility into your current spending and unlocks continuous optimization opportunities as your environment evolves.

With real-time monitoring, AutoSavings helps you stay proactive in managing cloud costs and identifying waste before it grows.

Is any special setup required to use AutoSavings?

No special setup is required.
Once you register your cloud account and activate the AutoSavings subscription, AWS cost optimization begins automatically—no manual configuration needed.

However, some savings recommendations may involve actual purchases or changes to your commitments. In these cases, your prior approval may be required. You’ll be notified through the OpsNow console, where you can review and approve the actions before they are applied.

AutoSavings allows you to start optimizing your cloud spend quickly, while still maintaining full control over key decisions.

How frequently does AutoSavings optimize RI and SP usage?

AutoSavings continuously monitors your AWS usage patterns and updates its optimization strategy on a weekly basis.
Based on the latest data, it adjusts the following:

  • New purchase recommendations for Reserved Instances (RI) and Savings Plans (SP)
  • Modification of existing commitments
  • Resell strategies for unused or underutilized commitments

This weekly optimization cycle ensures that your cost-saving strategy adapts in real time to changing workloads—maximizing efficiency and minimizing waste.

How is AutoSavings different from other Savings Plans or Reserved Instances tools?

Most traditional cloud cost tools mainly focus on monitoring usage or offering optimization recommendations for Reserved Instances (RI) and Savings Plans (SP). These tools typically rely on the user to take manual action, and they do not guarantee actual savings.

AutoSavings goes beyond simple recommendations by automating the entire optimization process. It uses your real AWS usage patterns to automatically purchase, adjust, or resell RI and SP commitments to generate measurable cost savings—without manual intervention.

In addition, AutoSavings operates under a performance-based pricing model. You are only charged a fee when actual savings are achieved, meaning there’s no risk of paying for ineffective recommendations.
This model ensures that customers experience real financial benefits, while OpsNow shares accountability for the savings performance.

AutoSavings is not just a tool—it’s a trusted optimization partner that delivers continuous, tangible cost reductions.

Does AutoSavings automatically purchase Reserved Instances (RI) or Savings Plans (SP)?

Yes. With AutoSavings, there is no need for you to manually purchase or resell AWS commitments.

Based on continuous analysis of your AWS usage patterns, OpsNow automatically handles the purchase and resale of Reserved Instances (RI) and Savings Plans (SP) to maximize cost savings.
This fully automated process ensures that you maintain an optimized cost structure without manual effort or risk.

AutoSavings is especially helpful for organizations that lack the time or expertise to manage RI/SP commitments, offering a hands-free, efficient way to control cloud costs.

How do I register as a seller to resell RIs through AutoSavings?

To enable AutoSavings to automatically resell your unused Reserved Instances (RIs), you must first complete the official seller registration process on the AWS Reserved Instance Marketplace.
There is no "Resell Registration" button within the OpsNow console. Instead, you need to register directly through AWS.

✅ Registration Steps:

  1. Why registration is required
    • AWS requires seller registration to process payments and comply with tax regulations. You’ll need a U.S. bank account and tax information.
  2. How to register
    • Go to the AWS Reserved Instance Marketplace Seller Registration page
    • Submit U.S. bank account details via the Manage Bank Account section
    • Complete the Tax Interview form to provide your tax classification and identity
    • Once approved, AWS will notify you via email
  3. Integration with AutoSavings
    • After registration, OpsNow automatically recognizes the registered AWS account
    • Your Reserved Instances will then appear in the AutoSavings Inventory tab, and the resale feature will be activated if eligible

⚠️ Note:

You do not need to manually notify OpsNow after AWS approval—AutoSavings syncs registration status automatically.
However, resale optimization will not begin until AWS seller registration is complete.

What is AutoSavings?

AutoSavings is a performance-based cloud cost optimization service built specifically for Amazon Web Services (AWS).
It helps organizations reduce unnecessary cloud spend by automatically optimizing Reserved Instances (RI) and Savings Plans (SP).

✅ Key Features:

  • Automated RI/SP Optimization
    AutoSavings analyzes your usage patterns and automatically purchases or adjusts RI and SP commitments to reduce reliance on expensive on-demand pricing.
  • Reselling Unused Commitments
    Any underutilized commitments are automatically resold through the AWS RI Marketplace to prevent waste and recover costs.
  • Real-Time Strategy Updates
    The system continuously monitors changes in cloud usage and updates optimization strategies accordingly.

💰 Pricing Model:

AutoSavings follows a Pay-as-you-save model, which means:

  • You only pay a fee when actual savings are achieved
  • There are no subscription fees or upfront charges

This makes it a low-risk, results-driven solution for AWS cost optimization.

I want to see a demo.

If you wish to request a demo, please provide basic information on the demo request page.

Our cloud experts at OpsNow will contact you.

Can't find what you're looking for?

Trusted by global teams to cut costs without compromise

OpsNow’s AutoSavings helped us seamlessly switch from Reserved Instances to Savings Plans, giving us the flexibility to scale.
Their blend of ML automation and hands-on support consistently maximizes our savings—even during unexpected changes.
"We only pay when we actually save."
OpsNow helped Juvo identify and reduce RDS costs, allowing us to fine-tune our databases and eliminate unnecessary overhead.
"Last month, we saved 11% on our AWS bill using AutoSavings."
I strongly recommend using it.
OpsNow is a valuable tool to help us gain control over multi-cloud environments, optimize costs, and improve operational efficiency.
"The AutoSavings feature helped us save 10% on our monthly cloud cost."