+90 850 346 48 21Sales team
FibaCloud
Cloud panel

MARKETPLACE / APP PARTNERS

Bring a well-prepared application to the conversation.

Have software that could help FibaCloud customers build or operate their projects? Share its purpose, deployment requirements and maintenance approach with our team so we can discuss a suitable Marketplace integration.

Discuss an app listing Browse the catalogue
APPLICATIONS / CLOUDFIBACLOUD
From a documented proposal to an agreed integration
Application context Deployment decisions Maintenance planning

01 / THE STARTING POINT

A useful listing starts with a clear deployment experience.

A Marketplace application should help customers understand what they are deploying and how to operate it. Begin with the problem your software solves, the users it serves and the components required for a working installation. Link to documentation that describes the actual product rather than only a promotional landing page.

Contact the FibaCloud team to discuss your proposed application. The existing submission route is a conversation through our contact page. Listing scope, technical integration, responsibilities and any commercial arrangement need to be agreed for the particular application; sending details does not automatically publish a listing.

01

Explain the customer outcome

Describe the workload, the users and the first successful task they should be able to complete. This gives the proposed listing a concrete purpose and a useful demonstration path.

02

Make installation reproducible

Document the supported operating environment, dependencies and configuration sequence. Identify which settings are provided at deployment and which the customer must complete afterward.

03

Own the maintenance story

Explain release updates, compatibility and the route for reporting problems. Customers need to understand how the application remains usable after its first installation.

02 / THE APPLICATION BRIEF

What to prepare for the discussion.

A clear brief helps the team understand the application, its dependencies and the responsibilities needed for a maintained deployment.

Project identity and documentation

Provide the application name, project or vendor website, documentation links and a contact who can discuss the integration.

Supported deployment environment

Describe the operating system, runtimes, services and resource requirements supported by the application. State any separate components needed for a representative deployment.

Configuration and access

Explain installation steps, network exposure, initial account setup and how deployment secrets are handled. Include the checks that demonstrate a usable installation.

Data and recovery

Identify persistent data and configuration, describe the supported backup procedure and explain the restore or migration requirements.

Licensing and commercial scope

Link to the applicable software license and identify any paid editions, usage conditions or third-party entitlements required by the proposed image.

Updates and support ownership

Describe supported releases, the update process and who maintains the image and application documentation. Provide the appropriate support or issue-reporting route.

THE OPERATING VIEW

From a documented proposal to an agreed integration

A proposed collaboration flow. Listing and maintenance arrangements are agreed for the individual application before publication.

  1. 01Application brief
  2. 02Technical discussion
  3. 03Deployment scope
  4. 04Maintenance plan
From a documented proposal to an agreed integrationA proposed collaboration flow. Listing and maintenance arrangements are agreed for the individual application before publication.Application briefTechnicaldiscussionDeploymentscopeMaintenanceplanFIBACLOUD / PARTNERPLANNING VIEW
A proposed collaboration flow. Listing and maintenance arrangements are agreed for the individual application before publication.

FROM PLAN TO OPERATION

A practical route to an integration.

Use the existing contact route to discuss the proposal and agree responsibilities.

  1. 01

    Prepare a concise application brief

    Use the checklist to describe the product, intended users, deployment requirements and ownership. Include links to the documentation and a representative operating workflow.

  2. 02

    Contact the FibaCloud team

    Send the brief through the existing contact route. Explain any technical or commercial questions that need to be resolved before a listing can be considered.

  3. 03

    Discuss the integration scope

    Review the proposed image, customer configuration steps, validation process and responsibilities with the team. Confirm the agreed path before preparing a public listing.

  4. 04

    Define maintenance expectations

    Document how releases, compatibility changes and support information will be kept current if the integration proceeds. Keep the customer-facing guidance aligned with the maintained image.

PRACTICAL QUESTIONS

Before you move forward.

Clarify the application and operating requirements before choosing the deployment.

Discuss your requirements
How do I submit an application?

Use the contact page to introduce the application and share the project, documentation, deployment and maintenance details in the checklist. The team can then discuss the proposed integration with you.

Will submitting details publish my application automatically?

No. The application and integration scope need to be discussed and agreed before publication. Avoid presenting an unconfirmed proposal as an available FibaCloud Marketplace listing.

Can commercial software be proposed?

Describe the licensing model, required entitlements and intended customer experience in your brief. The applicable commercial and technical arrangements need to be discussed for the particular application.

Who will maintain an accepted application image?

Maintenance and support ownership must be agreed as part of the integration. Explain your proposed release process, compatibility policy and documentation responsibilities when contacting the team.

THE CLOUD FOUNDATION

Plan resources alongside the application.

Review the infrastructure and guidance your application will depend on.

FIBACLOUD / App partners

Tell us what your application makes possible.

Share the project, documentation and deployment requirements with the FibaCloud team.

Contact the team Back to the catalogue

Your privacy matters

We use cookies to provide our services and for analytics and marketing. To find out more about our use of cookies, please see our Privacy Policy and Cookie and Tracking Notice. By continuing to browse our website, you agree to our use of cookies.
Settings