Hi there! While Port does not allow you to develop applications directly inside the IDP, there are are a few different approaches Port provides: 1. Self service actions - Actions like scaffold can help you develop applications. 2. Aggregations and calculations - Port allows you to analyze and perform calculations + aggregation on the data that is inside Port. Port leverages the fact that you ingest the data into the catalog, allowing you to do more operations on the centralized data catalog. If you want to talk more, feel free to email our team at [email protected] :)

We don't provide template managing, but we have templates that can be used to set up. Feel free to email [email protected] for more info :)

Thank you! Check out our live pre-populated demo to explore further: demo.getport.io/

Hey there! Of course! you can take the results of an action and ingest them into Port's software catalog as new entities or properties for existing entities. For example, if we look at a - create K8s cluster action, as part of the action the cluster itself would be created and it makes sense to create an entity inside the catalog for that new cluster. In addition, once that cluster is up and running, it is very simple to take its kubeconfig file and ingest it as a YAML property onto the new cluster entity. This can all be done via Port's REST API and other integrations (such as the K8s exporter), and then reflect inside Port that the self-service action has completed successfully once all of the required steps finished

Thank you! Yes, before preparing the webinar I looked at all the existing Port demos and tried to present something that was never done before. And I think using Terraform for Port is one of the big selling points.

Thank you for your feedback! You're welcome to join our Slack Port Community, to get Port support and share knowledge with other Port users: join.slack.com/t/port-community/shared_invite/zt-1x1iys4cn-oihCQp_ropEdIUIcKESImA

The data you see in the graph is made up mostly from K8s and Git resources ingested to Port and tied together using relations inside the catalog. You can view all of the JSONs used in this webinar, as well as a step-by-step guide to setup a similar portal in our public GitHub repo for this webinar, you can find it on github - github.com/port-labs/e2e-idp-webinar-may-23

@@getport Thank you for the work you are doing. I've enjoyed my experience with Port, but there's one point I'd like to ask you. If the company has many products, enviroment for individual team, how will it be organized in Port, about Service, monitor, Jira, system... Can you make a video or share your experience on that?

Hi @@andrewnhien9714 ! Port is made by design to be extensible and support any use case, architecture, and infrastructure layout you want to model. As such, it is easy (and also recommended) to ingest data from and integrate Port with a plethora of systems. After you have the data in place, you can use the UI interface to create custom views with the different filters and groupings that make sense for you the consumers in your organization. We have plans to post a webinar around the topic of custom integrations and managing data layouts in Port, so I suggest checking it out when it is released!

We'll make more soon! thank you for the enthusiasm :) In the meantime, feel free to join our Slack Port Community and stay updated on anything Port: join.slack.com/t/port-community/shared_invite/zt-1x1iys4cn-oihCQp_ropEdIUIcKESImA

Hi Felix! We're working on a version of Port that can be used in the customer's cloud. to apply for the beta write to us at [email protected] :)