AppFog was a cloud-agnostic application and infrastructure management platform used to manage workloads across on-premises and third-party cloud environments. It has been discontinued.
$0
BMC FootPrints
Score 8.2 out of 10
N/A
BMC FootPrints is an IT service management (ITSM) solution featuring workload automation.
N/A
gcloud CLI
Score 8.8 out of 10
N/A
The Google Cloud CLI is a set of tools to create and manage Google Cloud resources. Its tools can be used to perform many common platform tasks from the command line or through scripts and other automation.
N/A
Pricing
AppFog (discontinued)
BMC FootPrints
Google Cloud CLI
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
AppFog (discontinued)
BMC FootPrints
gcloud CLI
Free Trial
No
No
No
Free/Freemium Version
Yes
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
AppFog (discontinued)
BMC FootPrints
Google Cloud CLI
Features
AppFog (discontinued)
BMC FootPrints
Google Cloud CLI
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
AppFog (discontinued)
6.5
2 Ratings
18% below category average
BMC FootPrints
-
Ratings
Google Cloud CLI
-
Ratings
Ease of building user interfaces
7.01 Ratings
00 Ratings
00 Ratings
Scalability
5.32 Ratings
00 Ratings
00 Ratings
Platform management overhead
6.02 Ratings
00 Ratings
00 Ratings
Workflow engine capability
6.01 Ratings
00 Ratings
00 Ratings
Platform access control
6.01 Ratings
00 Ratings
00 Ratings
Services-enabled integration
6.62 Ratings
00 Ratings
00 Ratings
Development environment creation
7.42 Ratings
00 Ratings
00 Ratings
Development environment replication
8.42 Ratings
00 Ratings
00 Ratings
Issue monitoring and notification
6.01 Ratings
00 Ratings
00 Ratings
Issue recovery
6.42 Ratings
00 Ratings
00 Ratings
Upgrades and platform fixes
7.02 Ratings
00 Ratings
00 Ratings
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
AppFog (discontinued)
-
Ratings
BMC FootPrints
8.1
9 Ratings
2% below category average
Google Cloud CLI
-
Ratings
Organize and prioritize service tickets
00 Ratings
9.09 Ratings
00 Ratings
Expert directory
00 Ratings
7.04 Ratings
00 Ratings
Service restoration
00 Ratings
6.02 Ratings
00 Ratings
Self-service tools
00 Ratings
7.07 Ratings
00 Ratings
Subscription-based notifications
00 Ratings
10.06 Ratings
00 Ratings
ITSM collaboration and documentation
00 Ratings
9.06 Ratings
00 Ratings
ITSM reports and dashboards
00 Ratings
9.07 Ratings
00 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
AppFog (discontinued)
-
Ratings
BMC FootPrints
7.9
7 Ratings
4% below category average
Google Cloud CLI
-
Ratings
Configuration mangement
00 Ratings
7.77 Ratings
00 Ratings
Asset management dashboard
00 Ratings
8.05 Ratings
00 Ratings
Policy and contract enforcement
00 Ratings
8.04 Ratings
00 Ratings
Change management
Comparison of Change management features of Product A and Product B
AppFog (discontinued)
-
Ratings
BMC FootPrints
9.0
4 Ratings
5% above category average
Google Cloud CLI
-
Ratings
Change requests repository
00 Ratings
9.03 Ratings
00 Ratings
Change calendar
00 Ratings
9.03 Ratings
00 Ratings
Service-level management
00 Ratings
9.04 Ratings
00 Ratings
Cloud Management
Comparison of Cloud Management features of Product A and Product B
It was very good to use in small scale projects. Considering the high end projects with many instances and multi-platform architectures, it is better to test before the application is deployed. I think few of the questions can be general - who are the system users and what size is the application focussing on? How much resources are required? Will the application require any additional services?
BMC Footprints is so well suited to keep the documentation easy to read and find, as same as typification. You can find specific documentation for an audit so fast and export a report using the specific criteria that you need to comply with your boss or audit needs. As I told before, BMC footprints need to be more friendly to the end users because they get lost many times trying to track some ticket or typing documentation.
it is great for automating tasks like deploying VMs, running BigQuery and managing cloud resources at scale. It is much faster than the UI for repetitive actions and allows you to easily script and scale progress. However it is not ideal for beginners
Documentation. We try to reduce the amount of paperwork needed for staff to do their job, so by automating certain tasks, we are able to speed up the resolution process for trouble tickets.
Reporting. We'll use the reporting tool to get the number of tickets opened, response times and can go into granular reports.
Surveys. When tickets are closed, we automatically send out surveys to end users to get valuable feedback on how we did and what we can improve.
Purpose based configuration- It would be beneficial to see a more purposed based, out of the box, configuration option. For example, if you need PCI compliance, more intuitive reporting would make managing compliance much easier.
Initial design and implementation- Don't think that your experience as an IT professional will allow you to stand this system up on your own. To properly configure Footprints and set yourself up for success down the road, get Professional Services with this one.
Somewhat behind the times- Service Core is making a huge leap forward with the latest version, 12, but Asset Core is far behind. There are quite a few quirks to how the application works and how it is used.
It has been the business decision to go with them and that is what we will do. Going back, this would have not been the choice, but nothing can be done about it now. We are stuck with this application for years to come. Wish there were other possibilities that could be done.
It's so simple to use and customize however you want. You can create new workspaces and workflows with ease, set up new users, incoming email rules, customize the layout of the forms, and even change the colors and logos. It's just very easily customizable overall. It's also really straightforward to figure out how to use, you really almost don't have to show somebody how to use it. If you just sit them down in front of it and let them look it over, they could figure it out themselves easily.
Google Cloud CLI is highly usable once you’re past the basics, especially for engineers and DevOps teams who live in the terminal. It’s powerful, consistent, and scriptable, which makes it excellent for repeatable workflows, automation, and day-to-day cloud operations. The command structure is generally logical, tab-completion and help flags are solid, and it integrates cleanly into CI/CD pipelines—huge wins for productivity
I've had no issues with the support for FootPrints. We haven't really had to use them all that much over the years, but when needed they have always been prompt and knowledgeable at dealing with any issue. I've worked with a lot of different support teams over the years, and they have been one of my favorites to work with.
Primarily because it used to have a good free tier earlier, which it does not anymore. It's simple, and things are available to use. Compared to it's competitors, it does has less features, but that kind of acts in its favor. That adds to the simplicity, and ease of use for a new user.
I was not involved in the selection process but in my opinion either SQL or Access databases would have worked just as well without the same amount of cost. These two systems would have been much easier to manage and would have tracked the same information in a less convoluted process and expense.
Google Cloud CLI stacks up well against other cloud and infrastructure CLIs by balancing power, consistency, and automation readiness, especially in production environments. Compared to AWS CLI, it’s more opinionated and readable, with better defaults and a more coherent command structure across services. Compared to Azure CLI, it’s less beginner-friendly but offers deeper control and is better suited for complex, large-scale workflows.