Website maintenance agencies can actually schedule.

It's application security meets project management and planning. Metaport is ideal for teams that struggle to provide data to teams for advanced EOL, security and maintenance planning.

By using Metaport's lifecycle chart and shared maintenance calendar. Sharing the chart and calendar with customers and teams, levels the playing field: Everyone knows where maintenance is at.

You can also try our isitendoflife.com tool and find out what's nearing EOL for your teams' Django, Drupal, and Laravel projects.

Not really, but there are overlaps (and Metaport does integrate with it). Dependabot automatically issues PRs for outdated and insecure dependencies but it can't tell you what's end-of-life, and it's also Github only.

Metaport doesn't need a VCS because it's technology agnostic. It gives your team the heads-up about end-of-life software too, so you can lock in upgrade pipelines sooner with your customers.

Software spends most of its life in a maintenance phase, so reducing unbillable time spent digging for end-of-life, security and maintenance data - which Project and Account Managers need for planning and budgeting - is critical.

Metaport provides the data automatically, and well before end-of-life dates hit.

Metaport is about teams first and foremost, specifically; Project Managers, Delivery Leads, and Account or Relationship Managers, as these roles need data - the sooner the better - in order to plan with their customers.

That said, we encourage engineers to use it too, they just don't normally require the macro-view which Metaport optimizes for.

Your customer's projects run an agent which gathers information about applications in production (or UAT, or wherever) and sends it securely to Metaport over SSL (or encrypted email). Metaport notifies and presents the data for your team to begin its planning effort immediately.

DependencyTrack, Dependabot, JIRA, and Keycloak. And because it's open source at its core, developers can create new integrations easily.

Yes and No.

"Yes" because Metaport does deal in application security and maintenance data. "No" because your existing SAST, AppSec, and ASPM tools only deal in individual things: repos, container images, and codebases. They're also intended for use only by technical roles.

But without a portfolio-wide view, your team is missing issues identified in one app, which may exist in some or all of the others.

Metaport provides portfolio-wide visibility and is designed for Project Managers and Account Managers (as well as engineers and security) who all need to know where their clients' apps are at while avoiding unnecessary technical complexity.

Probably! Metaport is technology agnostic and accepts data in a neutral format from any modern website or web application technology stack. It works directly with your production Node, PHP, Python, and .Net apps.

Yes! Metaport is designed to be run in containerised environments, review our Docker Hub here.

Yes! Metaport reduces operational risk and provides teams with the portfolio-wide insights they need to stay ahead of software updates and vulnerable components.

Review the pricing section. The SaaS is designed for use by teams and there are per-application, and per-user limits.

However we want you to tell us what you think it's worth.

At its core, Metaport is open source software which means it's also available to be self-managed on-premise. A support package is also available for USD $79pm, where we manage it for you. Please contact us for more information about support or the SaaS.

Visit the pricing section. Metaport on-premise is available today, and we're building-out the SaaS. Take the survey and tell us where your price point is or head to our docs site to get started with Metaport CE.

Yes! We're here to help. Get in touch with us directly or check out our documentation.