Home » Fedr8

Category Archives: Fedr8

Fedr8 Green Rain now available to 260,000 global customers in the AWS Marketplace

18th June 2020 / Leave a comment

Fedr8 is pleased to announce that after extensive testing, Green Rain has been accepted by AWS and is now available for subscription to 260,000 global customers on the AWS Marketplace.

Many organizations want to run Green Rain inside AWS accounts they control because:

  1. They want Green Rain to analyze their code without that code being transferred outside of their control.
  2. They want to deploy Green Rain their own accounts to meet compliance rules.
  3. They want to purchase Green Rain on a pay-as-you-go consumption model.

This is especially important for global systems integrators who have multiple complex enterprise customers and many AWS accounts. By using the AWS Marketplace, they can access their software subscriptions from anywhere in the world and deploy to any AWS accounts they manage for their clients.

How it works

To get Fedr8 Green Rain from the AWS Marketplace:

  1. You can purchase by the hour or with Bring Your Own Licence (BYOL) which means customers must have a licence agreement in place already with Fedr8 – get a licence here.
  2. Go to the Fedr8 page on AWS Marketplace and buy a subscription.
  3. Launch your own Green Rain instance in your AWS account.
  4. Customers only pay for the applications they analyze. They can have as many instances of the software as they need.
  5. Green Rain runs on an EC2 instance in your AWS accounts and you pay for the EC2 resources consumed. Usage and billing is all handled via the AWS Marketplace.

Damion Green, Fedr8 CEO, said: “We wanted to make Green Rain simple to use in customer cloud environments. All customers need to do is get a licence from Fedr8 then get the software from the AWS Marketplace. It means they can plug Green Rain into their workflow and get insights into code within an hour of subscribing. They control where their code lives, and how Green Rain integrates. And if they get stuck, the Fedr8 team are here for support, but mostly we’re hands-off.”

For more info on Fedr8, Green Rain and to go to AWS Marketplace, click here

NCSC cloud anti-pattern #4: Don’t build an ‘on-prem’ solution in the cloud – Fedr8

7th May 2020 / Leave a comment

NCSC cloud anti-pattern #4: Don’t build an ‘on-prem’ solution in the cloud

Lifting-and-shifting (Rehosting) is perceived as the easiest, Occam’s Razor method of migrating applications from on-premises to the cloud. Rehost is the defacto standard migration method for large-scale migrations where time is of the essence. “Let’s get it done and finesse it later,” goes the refrain.

As long as you configure the cloud to be similar to on-premises then your application is compatible and requires no changes. Vendors will promise, “Just make the cloud look similar to on-premises then you can drag-and-drop your application from one to the other.” Painless, right? Not according to the National Cyber Security Centre (NCSC).

In their 2019 whitepaper, “Security architecture anti-patterns”, NCSC recommend *not* treating the cloud the same as on-premises. Like all good security recommendations, this is based on common sense.

It is a fact that when you lift-and-shift to Rehost your application to the cloud you will also:

  • Lift-and-shift the issues you had on-premises into the cloud.
  • Fail to exploit the advantages of the cloud.

It’s possible to understand some of your exposure to this anti-pattern. Using discovery tools to map your on-premises infrastructure and applications to infer how you might refactor and replatform for the cloud and build migration plans that do not include security anti-patterns.

You need two-perspectives to discover the anti-pattern

Infrastructure-centric tools only tell you the bottom-half of any application story because the application is an opaque entity to infrastructure tools.

Bottom-up infrastructure reports might only list the server name and its address on the network. Or, like the AWS Server Migration Service agent, it might list the processes and network ports inside the server.

This is the “edge” of the application, where it touches the infrastructure, it is not inside the application. You can discover that “MySQL” is running on “port 3306”, and they might even tell you that a Java application is running on the server (because a JVM process is running) but they can’t tell you what that Java application is doing:

  • Which database is it using, and how?
  • Is the application logging to local disk?
  • Is the application using on-server session management?
  • Is the application sending emails to an on-premises server?
  • Are there hard-coded IPs for on-premises resources?

This is where the application-centric Fedr8 Green Rain engine complements infrastructure tools and completes the picture by analysing the application code to answer these questions and more.

Replatform and refactor to fix anti-pattern #4

Each of these technical dependencies is an opportunity to implement the recommendations from the NCSC white paper to “use higher-order functions in the cloud”.

Cloud consultants use the Green Rain technical report in the early assessment phase to define work packages. For example, if a hard-coded IP is found, the work can involve understanding what that remote service is and if it’s critical or can be disregarded. Application owners also benefit because Green Rain reveals technical dependencies at the line-of-code level from inside the application.

In effect, Green Rain creates a joint perspective between infrastructure and application owners. This is missing from many cloud migration projects.

Green Rain is also used in post-migration to analyze the code of already-migrated applications. By discovering if they applications are exposed to the NCSC anti-pattern #4 it’s possible to uncover more opportunities to optimize the application for the cloud.

Application refactoring and replatforming is not just about fixing and mitigating security risks. Adapting your application to exploit the cloud can return significant benefits. Comic Relief reduced their cloud spend from £83k per month to £5k per month.

Getting started with Green Rain

Contact Green Rain and we can help you analyze your application whether it’s on-premises today or already in the cloud. You’ll get access to an experienced cloud and application migration consultant who can guide you through the two-step process:

  1. Analyze your application with Green Rain
  2. Use the Technical Report to build your own migration or remediation plan

More resources

Learn more about how Fedr8 Green Rain can help you.

Kelsey Hightower: Why modernizing at the infrastructure layer is half the problem – Fedr8

22nd April 2020 / Leave a comment

How Green Rain provides insights to the 6Rs of migration

Lifting-and-shifting virtual machines from on-premises to a cloud can treat the application as a fragile black-box.

To make this black-box operational in the cloud without adapting it means you have to change the environment — the cloud — to fit the black-box. This is great news for vendors like VMware because they specialise in “normalizing cloud” to look like the same everywhere.

However, it means your application is not adapting to exploit the cloud and you are likely missing out on big benefits. Look at Comic Relief who refactored their app to reduce monthly costs from $83,000 to just $5,000. That is not possible without opening the black-box and changing it.

The inimitable Kelsey Hightower of Google recently tweeted that migrations are lacking an application perspective:

The answer for businesses is to look at the code they own — not 3rd party products — and see if it’s cloud ready, or container ready and what their license exposure is.

The black-box challenge

Even if you know that you need to open that application black-box and adapt it: can you?

  • It cannot be assumed that the application is perfectly supported with in-house expertise in all technical aspects of the application.
  • It cannot be expected that the application documentation is complete and up to date. Expect missing, out of date and plain wrong documentation.
  • It’s not a given that you have the time or resources available to focus on reviewing the application.

Ideally what you need is a helping hand to get going with the application analysis. A new addition to your team that is an expert in analysing all modern application languages and knows about cloud, containers and licensing.

This new member of your team is called Green Rain.

Analyzing the application layer with Green Rain

Green Rain answers the “application layer” part of Kelsey’s tweet:

  • The application’s code is the source of truth: not just an interpretation in developer’s heads and the documentation.
  • By analyzing the code, Green Rain can identify technical dependencies that are risks and/or opportunities in the cloud.
  • A cloud expert takes the Green Rain application analysis to define the investment required at the application layer.

For example, the following screen shot shows some technical dependencies that Green Rain has discovered that requires application investment.

Bar chart showing the number of discovered technical dependencies by category

In the chart above, Green Rain is advising you to invest in the following to prepare the application for cloud readiness:

  1. Look at local DiskIO writes and consider cloud patterns to modify these to fit ephemeral and immutable virtual machines or containers.
  2. Make sure the email service is accessible from within the cloud, or migrate to a cloud mail service.
  3. Modify logging from local server to distributed cloud logging service.
  4. Consider moving from server-based self-managed database to cloud database service. Potential database migration.
  5. Consider moving from local server state management like sessions to distributed session management in the cloud to allow for autoscaling.

The key findings from Green Rain show you where the break-points are on the edge of your application.

That is, where Green Rain discovers your application is dependent on something that is commonly different in the cloud, it tells you so you can consider it and take action.

How to add Green Rain to your team

Green Rain is really easy to use. You can:

  • Use a Fedr8-hosted version
  • Get a virtual appliance to run on yours or your clients’ premises or cloud

All you need to do is contact us below and we’ll get you up and running in no time. You’ll get access to one of our cloud application experts to understand your situation, guide your analysis and help you build your unique application migration and remediation plan.

Five things your code can tell you about migrating to AWS – Fedr8

6th April 2020 / Leave a comment

steve.chambers@fedr8.com

April 2020

Applications are the cogs in your business value stream, and applications are made of code. When it comes to planning cloud migration and application modernization for your business, it’s fundamental that you ask questions of your code.

Questions like

  • What will break?
  • What can I optimize?
  • What is the risk?
  • What is the effort?

These questions are not always answerable by developers or documentation. Why? Because it’s a fact of life that developers have moved on and documentation is incomplete. Without asking these questions and finding the answers, application modernization and cloud migration can be like flying blind in fog through a mountain range: it’s risky and the crash could be fatal or very expensive.

The top five common Green Rain discoveries

We repeatedly discover the same five technical dependencies that might break in the cloud out of the hundreds of gotchas that Green Rain can discover in your code.

These offer an opportunity to do things in more cloud-ready way:

  1. User session/state management
  2. Database technology
  3. Third-party services
  4. Local disk I/O
  5. Logging

These are really common. There are a few hundred technical dependencies that the Green Rain engine has been taught to find in all the popular modern languages. It also knows whether these dependencies are critical for different clouds such as AWS, Azure and Google.

How does it work?

Green Rain isn’t a simple pattern matcher. It’s not a rules engine. Green Rain is unique in that it’s a learning engine. Green Rain uses what it’s learned to go through every file in your codebase and infers things like complexity, entanglement and dependencies.

Being a machine learning engine, Green Rain gets the majority of discoveries right and some things wrong; just like a human, but faster and with more accuracy. And unlike a human, it can analyse a million lines of code in an afternoon, with:

  • No guidance from you.
  • No customization for your organization or application.
  • No custom rules.
  • No configuration.
  • No learning curve.
  • No huge and clever human resources to find and allocate.

Green Rain works out of the box: just import and go.

But Green Rain doesn’t replace humans. The report it produces is interpreted by a human that reads the signposts that are discovered. The human expert then uses these insights to develop a remediation plan to migrate and modernize the application. This human is usually a cloud migration consultant.

Green Rain is doing what computers do best: complementing its human friends by taking on the complex, gargantuan and mundane and leaving the humans to do the clever stuff on top.

Let’s look at the five common findings in more detail.

1. User session/state management

Perhaps the most common application technique that Green Rain finds is session management. This is how your application tracks things for users as they use your application. However, outside of the cloud, this might be done in a fragile manner by storing state locally on the server – in memory or on local disk in temporary files. If the server bombs, then so do all your user sessions. Imagine using your banking app and being logged out halfway through making transactions.

Session management is always an opportunity to fix fragility and use cloud architectures like distributed session management. Why not use an external, fast, Cloud Service Provider-managed cache like Memcached or Redis and refactor your code to use them instead?

2. Database technology

I remember the days when the same RDBMS from the same vendor was used for everything. Nowadays, different database systems are used for different purposes:

  • MongoDB for NoSQL
  • MySQL for SQL
  • Neo4j for GraphQL

Do you know what your application uses? You could ask a developer or check the documentation… but is that possible, and will it be accurate? By analysing your code with Green Rain you’ll find things like this:

Green Rain has worked out that — in your Ruby application — it’s using MySQL and has listed down some key files where the code is using it, to prove it to you, write down to the line of code. 

This app is definitely using MySQL — but so what? Using this, the human expert can decide:

  1. Yes, this is the only database engine this app is using.
  2. It’s MySQL so we can migrate it to the AWS and use their MySQL RDS instead of packaging our own.
  3. If this was Oracle, maybe we could have looked at migrating from Oracle to AWS Aurora

3. Third party services

On-premises, behind those high datacenter fences and thick walls, there are often shared IT services that your application can rely on for things like email and authentication: but what happens if you move your application to the cloud? Things break.

In this case, the application is expecting to speak with a Microsoft LDAP server. Can it connect if the application is running on AWS and the LDAP server is being those high datacenter fences and thick walls? 

Maybe you can create a VPN, or Direct Connect, or maybe use cloud-based authentication.

4. Local disk I/O

It’s normal for a long-living application on a long-living server to read and write from the local filesystem. And, of course, you can do this on virtual machines on the cloud. But should you?

Typically the things you find that an application is writing to the local filesystem are configurations and logs. These are all opportunities to replace them with more distributed, resilient and cloud-native technique. For example, instead of storing configs on the local filesystem, put it in something like AWS Parameter Store. It’s more secure and, well, just better!

5. Logging

If there’s one thing that’s probably, most definitely, needs to change when you move an application to the cloud, it’s logging. But how does your application do logging? Where is the logging code in your application?

This application was a enormous 562,000 lines and 6,100 files. Amongst all of that code, Green Rain has found 72 logging-related code dependencies in 34 files. Armed with this, the expert can start to work out the size of the problem and think of a cloud-based solution.

Logging is an important application subsystem that mustn’t break when you migrate it to the cloud: imagine your application not working properly in the cloud, but you aren’t aware because logging isn’t working either.

Logging is also a great opportunity for modernization and use modern observability techniques and cloud-based products for even better application insights.

Conclusion

Your application’s source code is the source of truth. It can tell you what can go right and wrong when migrating and modernizing on the cloud.

What Green Rain does is not feasible for a developer to do: go through thousands of files and lines of code and find hundreds of dependencies that may or may not break.

In our experience, an application’s documentation is often missing, incomplete, incorrect or out of date. You can find out some things from documentation, but how correct is it? Can you make decisions based on that kind of documentation?

It’s so quick to run a codebase through Green Rain it’s a no-brainer. It might confirm what you think you already know, and that’s valuable in itself. But it’s very likely that it will find a few things that you didn’t know. Armed with this uptodate and accurate knowledge, your experts can plan their way through the clouds.

Getting started with Green Rain

Green Rain can delivered in different ways: we can host it for you, or you can get a virtual appliance and run it on your premises or cloud.

How does an enterprise containerize their applications?

16th March 2020 / Leave a comment

How to use Green Rain to discover if your application can exploit VMware’s Tanzu or Amazon’s Bottlerocket

It’s typical for competitors — or frenemies — like VMware and Amazon to make competitive announcements in the same, short timeframe.

Recently it was VMware’s Tanzu announcement quickly followed by Amazon’s Bottlerocket. (No, I don’t know where they get the names from, either!) But container platforms are not new – Docker is very well established and our Open Source friends at Red Hat have had OpenShift container platform in customer hands for some time.

Before we explain what Tanzu and Bottlerocket are — and why you might or might not care — it’s important to start with your applications when considering containers. Mega-vendors are prone to describe the world from their world view, which can be “infrastructure-up” in the case of VMware and “cloud-up” from the viewpoint of Amazon.

At Fedr8 we believe enterprises should start from their world view, and in particular, be application-centric.

That’s why we built Green Rain to be the only application- and code-centric cloud, container and licensing insights platform.

How to discover if your applications are container ready

There’s no point knowing about Tanzu or Bottlerocket if your application can’t be containerized.

But how do you find that out? There are two main methods:

  1. Have an application expert look through the code, software architecture and documentation for a few weeks and make an experienced recommendation.
  2. Use Green Rain by Fedr8 to find out in a fraction of the time, effort and cost.

Green Rain can analyse a code base with a million lines and thousands of files and modules in just a few hours. This is impossible to do by human hand, eye and brain. Nobody wants that job.

Green Rain does the heavy-lifting with its deep-learning code-analysis tool to give code and cloud experts the information to containerize applications.

Green Rain’s Container Module

By importing your code repository into Green Rain you can, within hours, find out three important things about your application:

  • Cloud Ready – What might break if I migrate to cloud? What might I optimize?
  • Container Ready – Which parts of my application are container-friendly?
  • Licence Discover – Which vendors and products do my application use that require licensing?

If your head has been turned towards containers because of the Tanzu and Bottlerocket announcement, the first place to start is with the Green Rain Container module.

Green Rain Container Module showing potential container opportunities

Using this insight you can build up a picture of what opportunities there are for containerization: then, you can look at OpenShift, Tanzu and Bottlerocket as target platforms, just like you consider Docker.

What is VMware Tanzu?

VMware Tanzu is an evolutionary platform, combining the well-known Kubernetes (which emerged from Google back in the day) and VMware into one Cloud platform.

VMware continue to try to “own” the management space across clouds, infrastructure, virtual machines and now containers. It’s a one-stop-shop kind of thing, likely to be popular amongst existing VMware customers — of which, there are many! Tanzu is a management system that will orchestrate workloads… Amazon’s Bottlerocket is different.

What is Amazon Bottlerocket?

Amazon Bottlerocket is a container-friendly operating system.

Containers are a feature of Linux (and nowadays, Windows) operating systems.

It’s got easier nowadays, but back in the day, you had to be something of a Linux hax0r to get containers working. Then came along Docker to help build images and manage containers, but it was still a bit “command line-y”. Imagine Bottlerocket as an OS layer in a virtual machine that makes “doing containers” easy — you don’t need to be as much of a Linux hax0r to get all the benefits of containers.

Five steps to containerize an application

What does it mean to Containerize an application?

Application containerization is an OS-level virtualization method used to deploy and run distributed applications without launching an entire virtual machine (VM) for each app. Multiple isolated applications or services run on a single host and access the same OS kernel.

Containerization is, of course, a business decision and not just a technology decision. It always starts with Why, followed by What and ending with How.

  1. Why should we containerize? Is there a business case to containerize?
  2. What target platforms and architecture – Tanzu? Bottlerocket?
  3. How do I containerize my application?

For the technical containerization steps, this guide on Hackernoon by Henrique Souza is an excellent start.

A summary of Henrique’s process:

  1. Pick your base image wisely!
  2. Install only necessary packages
  3. Add your custom files — follow standards
  4. Define the user to run your container
  5. Define the exposed ports
  6. Define the entry point
  7. Define a configuration method
  8. Externalize your data (Green Rain helps)
  9. Make sure you handle logs “well” (Green Rain helps)
  10. Rotate logs and other append-only files

What to do next?

Don’t fly blind in the clouds.

Use Green Rain to analyse your most important source of truth: your code. Plug the Green Rain output into your Container project to help make the best-informed decisions.

Contact Fedr8 to talk about application-centric cloud insights such as Cloud Ready, Container Ready and Licence Discover.

Find out more

Comic Relief achieved 16x value with application-centric migration instead of infrastructure-centric

28th February 2020 / Leave a comment

Comic Relief changed their infrastructure-centric AWS bill from £83k per month to £5k per month.

Their 16x cost reduction was achieved by refactoring their application to exploit the cloud. But not everyone is refactoring their applications.

Rehost is the most common cloud migration strategy (40%) of the 6Rs. Also known as Lift-and-Shift, is a bottom-up infrastructure-centric migration approach:

  • To Rehost you have to replicate the infrastructure topology from non-cloud on-premises to the cloud (networks, security, storage, compute). Then you black-box migrate an application to its new home (usually copying a virtual machine and a dump of the database from on-premises to cloud).
  • Rehost is like kicking the cloud can down the road because you still have work to do on your application to help it exploit the cloud.
  • Rehosted workloads can benefit from some cost optimizations such as forward-contract purchasing of cloud resources (Reserved Instances), that is a welcome optimization and can chop 20-30% off your bill. Surprisingly, many companies don’t achieve this and still pay the full-price on-demand cost of cloud.
  • Rehost = minimum change = minimum cloud value.

You will never achieve the same savings as Comic Relief by rehosting your applications to the cloud. A 16x magnitude of savings is only possible by refactoring your application.

In this post, we compare and contrast Rehost with Refactor and describe how Green Rain by Fedr8 can help you get the best of both worlds.

The benefits and drawbacks of Rehost

The benefit of Rehost is its simplicity.

It requires only an infrastructure-centric understanding of the applications and data. Because the application isn’t changing, it is perceived as getting to the cloud by the fastest, cheapest path. Rehost is popular for mass-migration “factories”, especially where there is a deadline priority (e.g. datacenter end-of-contract/life is coming up).

The drawbacks of Rehost are four-fold:

  1. You are migrating all the technical debt and non-cloud practices (e.g. scripts, tools) into the cloud.
  2. You are not optimizing for the cloud which means that massive-sized and under-used on-premises VM is replicated to the cloud. Yes, you can optimize, but often this isn’t done because people are scared to make changes during migration.
  3. You are not leveraging cloud-managed services. For example, you still run your own database or load balancer instead of letting the Cloud Service Provider take the strain.
  4. You still have work to do when you arrive. Because you haven’t doing (2) and (3) above, then you have more work to do to become “cloudified”.

All of these drawbacks incur cost penalties.

Vendors like VMware recommend the Rehost approach because you need their software to make the cloud look like on-premises, and vice-versa. If you were doing Rehost from a VMware-dominated on-premises datacenter, then it’s tempting to migrate to VMware-on-AWS in the cloud to minimize changes, though there are higher costs to consider for this “ease of migration”.

Application-centric refactor

Refactor means modifying your application to use cloud services.

Evolving your application to a different architecture — for example, more microservices than monolith. There are new approaches to cloud applications called serverless. Refactoring can take considerable effort but the results can be fantastic, as Comic Relief found.

Read how Comic Relief swapped their monthly infrastructure-centric cloud bill of £83k for an application-centric serverless £5k.

Benefits and drawbacks of Refactor

Refactor means fully harnessing the power of the cloud.

The goal is to make your application cloud-native. It is impossible to be cloud-native without being application-centric. If you don’t understand your application, if you can’t modify it, you can never be cloud-native.

The drawback to refactoring is that you need the skills, effort and resource to evolve your application.

How Green Rain supports Rehost and Refactor migrations

Analysing an application for cloud refactoring with Green Rain

Bottom-up, infrastructure-centric cloud migration tools will analyze your infrastructure, help you configure and size the target cloud, and migrate your applications, data and databases to the cloud. But they do not understand your application code.

This is a migration blind spot, because:

  • You may be using session management that doesn’t work well in the cloud. In the cloud you need to use distributed session management.
  • You may be using just one SQL database but in the cloud you could use several types to suit the application (there are seven types of database in AWS).
  • You may be writing logs to local disk and saving state locally, which is an anti-pattern in cloud infrastructure where immutable and ephemeral servers scale out and in on-demand.

Know Your Application with Green Rain

If you want to refactor your application then you need to understand the code and what might break or what can be optimised for the cloud.

To Know Your Application means you need the application developer and maintainer to be available to contribute. Are they still employed? Is the documentation up to date? Do your talented software engineers want to work on a tedious cloud migration project or the latest cool whizbang widget?

Green Rain brings clarity to this blind spot by using a deep-learning engine to analyse your code repository and give you signposts about where you need to spend time refactoring.

The intelligent software inside Green Rain presents its findings through a user-friendly interface and tells you what dependencies are found and why they might break in a migration.

You can use Green Rain before and after Rehost and Refactor migrations to give you insights into your code and it’s dependencies on technologies that need to be addressed.

Next Steps

Learn more about Green Rain by Fedr8.

Talk to a Green Rain expert today and get a demo of what it can do for application-centric migrations. Your Green Rain expert can also arrange a trial on your applications on your premises to your cloud of choice.

Fedr8 and Rainmaker Solutions announce completion of first commercial project with Staffordshire County Council.

4th November 2019 / Leave a comment

Fedr8, the application discovery company, and Rainmaker Solutions, the business transformation specialists, announce the completion of their first technical project together.

Staffordshire County Council asked Rainmaker to build a business case and roadmap for moving out of their on-premises data centre and into the cloud. This project didn’t just involve comparing cloud and on-premises running costs, but factoring in the time as well as effort needed to migrate to the cloud so a programme could be created to drive changes forward effectively with funding secured.

Rainmaker had 10 weeks to complete this work and wanted to deliver the kind of detail that would normally require months of comprehensive application discovery. Aware of the client’s needs and with Rainmaker always looking to leverage new and innovative technologies to support our clients, Rainmaker engaged Fedr8 to analyse Staffordshire’s applications on their Green Rain application analysis platform. This was completed in one morning, including the uploading of Staffordshire’s applications source code to the platform. The immediate output meant that this part of the project could be completed in a much more efficient manner and to a greater level of detail than what would normally be expected, significantly reducing the time spent investigating, testing and ultimately delivering.

Tom Gouldon, Engagement Lead, Rainmaker commented:

“Estimating the time and expense to migrate in-house apps to the cloud used to take weeks and months of work – in a matter of hours we found applications that can be quick wins for migrations and for the rest we can build business cases supported by quantitative analysis. This is a real game changer for us in assessing readiness for the cloud.”

Vic Falcus, Head of ICT, Staffordshire County Council said:

“I was impressed with the functionality of the Green Rain software; the council has a reliance on some applications that were developed in-house, where off the shelf functionality was unavailable or to enhance digital processes delivered through our website. Any Business Case investigation around the cloud migration of a complex ICT estate requires analysis of a raft of variables to avoid unforeseen costs or unpleasant surprises down the line. Fedr8’s software has quickly and efficiently given us robust data around this aspect of the potential change.”

Damion Greef, CEO of Fedr8 added:

“The Green Rain application analysis platform yet again proves that no application needs to remain as a “black box” that can’t be moved updated or upgraded. Working with Rainmaker and Staffordshire we exposed the DNA of 5 key applications in one day.”

 

Fedr8

Damion Greef, CEO

Tel. 07823328816

Email. info@fedr8.com

Email. sales@fedr8.com                                                                             Web. www.fedr8.com

Fedr8’s Green Rain software solves one of the major IT problems in the world today: How does a company move to the cloud and capitalize on the efficiencies and economies that the cloud brings? The shift to cloud technologies and the digital transformation projects undertaken by large enterprise organizations pose many challenges, there are the unknown figures relating to cost and time for migration or transformation. In addition, there are unknown risks relating to relocating or changing the applications that support their businesses. Fedr8 reduces the risk in legacy software applications, identifies the most appropriate cloud to move to, accelerating the application analysis by 90% whilst significantly reducing the costs by 50%.

Fedr8 solves this problem using it’s proprietary artificial intelligence engine which interrogates software at a code level allowing the code in that software to be changed to suit the major cloud companies’ cloud platforms.

Our mission is to support our customers in embracing the business benefits of the adoption of the Digital Economies through accelerated adoption of Cloud Environments.

 

Rainmaker Solutions

All media enquiries to:

Linn Karppinen

Tel. +44 (0)7388498292

Email. linn.karppinen@rainmaker.solutions

Rainmaker Solutions is an independent business transformation specialist, with offices in London, Johannesburg and San Francisco. Working collaboratively, at the heart of the most challenging projects, Rainmaker helps organisations transform for the digital age by using its world-leading methodology to plan, implement, and embed lasting change.

Founded in 2010, Rainmaker has delivered exceptional results for clients including Amazon, Cambridge University Hospitals, Credit Suisse, Croydon Council, Department for International Trade, Direct Line Group, EBRD, the Food Standards Agency, HS2, and Newham Council amongst others.

For more information, visit https://rainmaker.solutions

Fedr8 CEO Damion Greef and Alan Green discuss the Green Rain cloud app migration solution.

18th October 2019 / Leave a comment

Fedr8 CEO Damion Greef and Alan Green discuss the challenges faced by companies and organisations in migrating IT infrastructure and legacy apps to the cloud. Damion explains how Fedr8’s Green Rain solution quickly resolve these issues, and provides a pathway to the cloud. Submit an app source code to Fedr8 at breakfast, and by supper Fedr8’s Green Rain will provide you with the answers for your app migration pathway.

Fedr8 Pathway signs partnership with Elevator/Fifty/One

23rd January 2019 / Leave a comment

Fedr8 Pathway signs partnership with Elevator/Fifty/One

Fedr8 Ltd the owner of the Green Rain machine learning software platform announces a collaboration with Elevator/Fifty/One, a US based professional services and migration specialist, to deliver both modern and legacy application migrations utilising the Green Rain software platform. Elevator/Fifty/One will deliver consulting, software re-development and migration – virtualization services to Fedr8 Pathway’s customers and partner ecosystem.

Elevator/Fifty/One will engage with Fedr8 Pathway to identify and deliver bespoke migration paths to current best of breed migration destinations. These services will include refactoring, containerising and managing application estates throughout Cloud migration projects.

By using Green Rain’s intelligent source code analytics, applications can be rapidly, cleanly, and efficiently optimised to make the most of cloud environments or infrastructure in terms of functionality, scalability and on-going costs. Providing superior ROI for clients compared to the “move to the Cloud at any cost” methodologies too often employed around the world.

Commenting on the tie up, Damion Greef, Fedr8 CEO said; “This collaboration with Elevator/Fifty /One, gives Fedr8 Pathway all the professional services required to deliver cloud migrations driven by Green Rain insights. The core mantra of the Fedr8 Pathway is to make informed insightful and rapid decisions to ensure optimisation of the target cloud environment. This approach avoids the risks involved of a generic “lift, shift and hope” approach, and delivers better cost control now and in the future.”

Leon Zackoski, CEO, Elevator/Fifty/One added; “Multiple Cloud Platforms coupled with a variance in containerization choice often creates risks, confusion and need for an appropriate “developmental direction”. The union between Fedr8 and EFO negates the risks or problems associated with ailing traditional rather “old-school” approaches to “moving to the cloud” Fedr8 provides the intellectual insight to achieve those foundational goals.”

Note to editors.

Green Rain circumvents the traditional limitations of a rule-based system to expose not only the genetic construct of an application, but the meaning and relationships embedded within the code visually.

Green Rain works by using “Molly” its proprietary artificial intelligence engine which interrogates software at a code level allowing the code in that software to be analysed producing actionable information at scale. Our mission is to support our customers in embracing the business benefits of the adoption of the Digital Economies through accelerated adoption of Cloud Environments.

About Elevator/Fifty/One

EFO is a US based company specializing in advanced software and hardware technologies. An extended emphasis on providing consulting, software development or -re-factoring coupled with data intelligence.

Contacts:

 

Damion Greef, CEO, Fedr8.                                                      Email.Damion.Greef@fedr8.com

Leon Zackoski, CEO, EFO                                          Email. l.zackoski@efiveone.com

 

END

Fedr8 CEO Damion Greef discusses the company’s new Pathway offering with Alan Green on Core Finance TV

18th December 2018 / Leave a comment

Damion Greef, CEO of Machine Learning Company Fedr8 explains how the company helps multi-level organisations migrate legacy applications to the cloud. He also discusses Pathway, Fedr8’s new one stop shop offering.

Post navigation

← Older posts
I would like to receive Brand Communications updates and news...
Free Stock Updates & News
I agree to have my personal information transfered to MailChimp ( more information )
Join over 3.000 visitors who are receiving our newsletter and learn how to optimize your blog for search engines, find free traffic, and monetize your website.
We hate spam. Your email address will not be sold or shared with anyone else.