Welcome to Frigg!
Developing integrations as easy as `npm install`
Last updated
Was this helpful?
Developing integrations as easy as `npm install`
Last updated
Was this helpful?
Welcome to Frigg Framework Documentation. Frigg is an open source serverless framework for developing integrations at scale. This documentation will help you get started with Frigg, understand its core concepts, and contribute effectively.
"TLDR, let me get my hands into the code!" ~ You, maybe
Sure, we hear you.
For our thorough readers, read on!
Frigg was built with the core principles that user-facing self-serve software integrations should be:
Easy to Develop
Inexpensive to run
Modular and Extensible
Easy to Scale
Easy to maintain
This is our answer to the question "hasn't this already been done before?"
Modern stack; easy to understand; fast to develop and deploy; comprehensive enough to cover any use case; fully open source. Interoperability, the way it should be.
These docs should be your go-to resource for all things Frigg related. Secondary are GitHub READMEs and Slack community channels.
In general, there are four main areas of the docs, and four supplemental sections
Frigg is the framework you would have built to develop integrations, if you had unlimited resources and time. The added difference is the promise of Open Source-- i.e. a community of developers collaborating to solve the same core set of problems over and over again. This is something you could never do internally.
The Frigg Framework is an opinionated set of development tools, modules, classes, and plugins built with modern software development teams in mind. Frigg will have you up and running out-of-the-box with a flexible set of tools to help rapidly add integrations that your end users can self-serve.
Frigg handles integration listing, authentication, and configuration out-of-the-box, built on a scalable serverless architecture. It includes a growing library of prebuilt API Modules to greatly reduce time to "wow." Along with the core "out of the box" features, the framework contains primitives to help address and flex to any use case.
A Frigg Application is predominantly a backend microservice, with an optional frontend. Most Frigg adopters already have an existing frontend UI built using a framework of their choice, or will bake integration UX into their product's core code. Frigg ships with a simple library of components to get you started quickly. See more details about frontend options here.
In the backend, Frigg is based on the serverless.com framework. This key piece of technology and the underlying compute/architecture under the hood provides a number of advantages:
Infrastructure-as-Code- The need to manually configure resources on the host provider is greatly reduced
Deployable to your favorite host- AWS, GCP, Azure, any a list of many more are available
Horizontal Scalability
Pay as you go
We are attempting to embrace a approach to documenting Frigg. Any recommendations are welcome!
Given these dynamics, partnership leaders often seek external vendors and tools to get integrations built. This search brings them to Frigg and .
Before you introduce Frigg to your engineering colleagues, partnership leaders should understand Frigg at a non-technical level. Our is intended to provide this context and support your internal advocacy for Frigg.
If you're ready to introduce Frigg to your technical colleagues, share this documentation site. Our is also instructive to both technical and non-technical audiences as well.
Have questions? Let's !
Read more about Frigg on .
Tutorials (Learning)
How-To Guides (Goals)
Reference (Information)
Explanation (Understanding)
API Modules
Contributing
Support
Roadmap