This message was deleted.
# platform-toolbox
s
This message was deleted.
d
Hi @Anshul Garg! In my opinion, we have to think of Backstage as a framework and not as a product. This is a good read about it: https://platformengineering.org/blog/backstage-implementations-for-more-than-100k-developers On the other hand, Port is a product. You can think about Port as an implementation of backstage(just an example I don´t know if used backstage) with some of the plugins added and configured to a specific outcome. If you need other features you can see Port integrations: https://www.getport.io/integrations or write your own custom integrations.
a
@damian gonzalez: Thanks for sharing I got your point.
h
Want something out of the box, port is the thing to get, want something to customize to your heart's desire backstage is what you want
That's not to say you can't customize port but as a saas product it will have limitations
a
Yes agreed !! But seems like soon they are coming up with other offerings apart from SAAS. Those are still under beta
r
Platform engineering teams are supposed to build internal developer portals, and using OSS will save $$$ also.
a
Eh, I’m not sure OSS saves you money
If you look at Backstage in enterprise for ~1k developers you probably need at a minimum: • 2 SWE (185k USD and 250 USD + equity) - deployment, modules, KTLO, 1 Senior Person, 1 Mid career Person (SV salaries) • Fractional TPM (150k USD * .3) - rollout, education • Fractional resources from security etc say: 50k annually • 2-3 instances in production say 5k yearly you’re looking at ~400-500k yearly for Backstage.
You can compare that to something at ~150-200k for something w/ a support contract + pre-canned educational materials etc. Potentially even cheaper…
Also most OSS starts bottom up (infra layer) vs from the requirements of customers internally. This creates some interesting dissonance as you try to integrate OSS data models into a real platform built for internal users. Backstage is an exception bc its spun out of a corporate setting but once the community gets ahold of it i find most OSS thats not enterprise backed tends to trend away from the user towards the maintainers POV
k
@Anshul Garg keep in mind that Port and Backstage are just IDP UIs for the most part. They don't do application delivery/CD etc. Those peices you still need to build and use. Rmember that IDP start with developer experience and how to make their lives easier to get code into production so that can focus on business value rather than deployment/infrastructure/devops etc aka non-functional requirements.
a
Talk to us at prodvana.io if you want to get things into production 🙂
@Kevin Scheunemann love that articulation - we see too often that BS/IDP is conflated as the “method to get into prod”. I think we will enter a state of: Service Catalog <-> Environment Manager
y
👋 Hey there! I'm Yair, part of the Port developer team. 🚀 What sets Port apart, in my opinion, is our commitment to creating an open platform where you can be an active participant. We're building a community and developing open-source tools that integrate with Port to make the usage of it as much OOTB 📦 as possible while mentainng the ability to customize it. Personally, using Port in our development cycle and I feel like it simplifies our day-to-day tasks. We recently introduced a new UI feature that that improved the operations setup, and I'm particularly excited about an upcoming project im working on: Ocean 🌊, an open-source framework that will make the development of a new integration to port a piece of cake. 😁 I fell in love with it, and I think many of you will too. Trust me, you won't be disappointed! 🌟
r
super insightful
l
We're working on making a detailed comparison matrix between vendors across 150-200 features, including Backstage and Port, and I think about 7 others. Should be ready in about 1-2 weeks. If you'd like, you can email me and we can set up a time to go over it together: lv@taloflow.ai
r
Hi @Louis-Victor Jadavji 👋 out of curiosity - what are the 7 others?
c
Hey @Louis-Victor Jadavji, did you finally released this comparison?
l
Hey @Romaric Philogène @Carlos Clemente I'm sorry for the delay. I'll be checking this group much more often going forward. I put together a quick Loom here to show you what we have. We got to 18 vendors actually. https://www.loom.com/share/ca2a7824ad414843a7e2af1892641370?sid=7bacf754-d89b-406c-a07a-350ff873a7b2 Please let me know if there are other tools you want to see or if you want the full report.
r
@Louis-Victor Jadavji What’s the purpose of your video
l
@Romaric Philogène Anyone can go run a comparison of platform engineering tools for their unique use case using our tool. A few people asked for our comparison matrix, so I'm showing how to use it
589 Views