The Fireworks developer integrations program supports tools, platforms, and projects in the LLMOps/Gen-Ops ecosystem, enabling seamless collaboration with Fireworks. 🌐 Whether through native integrations or compatible workflows, developer integrations represent tools and platforms that:

  • Offer native integration with Fireworks APIs, enabling deep functionality and seamless operation.
  • Provide compatible workflows, demonstrating interoperability with Fireworks through shared use cases and adaptable processes.
  • Add value to the Fireworks ecosystem by enhancing developer workflows, improving scalability, or solving key challenges in LLMOps/Gen-Ops. 🔧

​
Goals of the developer partners program

  1. Expand the ecosystem: Build a rich network of tools that extend Fireworks’ capabilities. 🌱
  2. Showcase interoperability: Demonstrate how Fireworks works with diverse tools to solve real-world challenges. 🌍
  3. Support innovation: Encourage the creation of impactful generative AI solutions. 💡
  4. Promote collaboration: Highlight shared contributions through joint marketing, workshops, and developer resources. 🤝

​
Types of developer partners

  1. Native integrations 🛠️

    • Tools with direct integration into Fireworks APIs or SDKs, offering seamless plug-and-play functionality.
    • Examples include official connectors, plugins, and platform integrations.

  2. Compatible workflows

    • Tools or platforms that interoperate with Fireworks through shared APIs, workflows, or third-party bridges.
    • Examples include vector stores, fine-tuning tools, and monitoring solutions that work alongside Fireworks.

​
What does a developer integration look like?

A developer integration can include:

  • Native integrations: Fully integrated tools or connectors offering seamless user experiences.
  • Workflow compatibility: Examples and documentation showing how a tool works with Fireworks APIs.
  • Developer resources: Contributed guides, notebooks, and sample repositories to enable other users.

Examples:

  • Native integration: A plugin for a vector database that directly connects with Fireworks’ RAG workflows.
  • Compatible workflow: A step-by-step guide for using Fireworks APIs alongside an MLOps monitoring tool.

​
How to apply

​
Step 1: Demonstrate compatibility or build integration 🔍

  • Native integrations: Develop a connector or integration directly into Fireworks APIs or SDKs.
  • Compatible workflows: Validate how your tool works with Fireworks workflows and APIs.
  • Prepare resources such as GitHub repos, notebooks, or workflow guides.

​
Step 2: Submit your application 📤

  1. Create documentation

  2. Submit your contribution

    • Fork the Fireworks cookbook and submit a pull request with your materials.
    • Include links to your GitHub repo or supporting documentation.

  3. Contact developer relations
    For guidance, reach out to DevRel.

​
Step 3: Review and feedback ✅

  • Fireworks developer relations will review your submission to ensure technical accuracy and alignment with program goals.
  • Once approved, your integration or workflow will be published in Fireworks documentation and promoted through official channels.

​
Benefits of becoming a Fireworks developer partner 🌟

  1. Ecosystem visibility

    • Be featured in Fireworks documentation and resources as a trusted integration.
    • Gain recognition within the growing LLMOps/Gen-Ops developer community.

  2. Technical and marketing support

    • Access Fireworks resources and technical support for building integrations.
    • Collaborate on co-marketing campaigns, webinars, and tutorials.

  3. Community collaboration

    • Join a network of ecosystem partners working to push generative AI innovation forward.
    • Share insights and learn from other projects in the LLMOps/Gen-Ops space.

​
Program FAQ ❓

Q: Who can apply to the Developer Partners program?
A: Tools, platforms, and projects that either integrate natively with Fireworks or demonstrate compatibility through workflows are welcome to apply.

Q: What types of contributions are required?
A: Contributions can include technical documentation, integration guides, sample workflows, GitHub repos, and co-marketing materials.

Q: Is there a cost to participate?
A: No, the Developer Partners program is free.

Q: Can compatible workflows evolve into native integrations?
A: Yes! Tools demonstrating strong adoption and compatibility may transition to deeper integrations and partnerships.

For more information or to get started, contact us at:

Was this page helpful?

Suggest edits