formkiq-core

Exactly. We'd love it if more people did that with our document management system. (https://github.com/formkiq/formkiq-core)

We use what might be called a microlith pattern with Lambda for our "infra meets code" document handling project (https://github.com/formkiq/formkiq-core). There's nothing stopping someone from taking what we have and porting to an EC2, but for most use cases, this pattern seems to work best. We break our Lambdas up by how they are used, to keep sizes down, with the option to break up further if we need to.

We may want to get in touch with each other. We have an Open Core document management platform that runs in AWS; I'm not sure about your roadmap, but there may be something there that's of use: https://github.com/formkiq/formkiq-core

I'm one of the co-founders of FormKiQ, an Open Source DMS that runs on AWS. After almost three years of development, we've finally reached the point (v1.11.1) where we think our project can go head-to-head with other document management systems when it comes to all of the expected functionality, including OCR, Encryption, Intelligent Document Processing, and Fulltext Search. FormKiQ deploys into your AWS account, but you can also try out our demo account via our website at https://formkiq.com Thanks!

One possibility is to use our open-core document management API build to deploy in your AWS account: https://github.com/formkiq/formkiq-core The files are stored in S3, with customizable metadata storage in DynamoDB. As the system is designed to run on AWS Serverless and Managed Services, the majority of the cost will come from S3 storage fees.

If you're not adverse to cloud file storage, FormKiQ Core (I'm a co-founder) is an open source document management system that runs on AWS and is designed to allow custom integrations. https://github.com/formkiq/formkiq-core

https://github.com/formkiq/formkiq-core API first designed document management system that deploys to AWS. Makes it easy to run standalone or to add Document Management functionality to existing applications.

The first point covered, giving away your core IP, is definitely one that resonates with me. We went open core with our headless document management system (https://github.com/formkiq/formkiq-core), and there is always a worry in the back of my mind that we are providing such a solid foundation with the open core/source components that we may be undercutting our enterprise modules. But on the other hand, I don't know that we're popular enough for someone to come along and build free modules on top of our product. So maybe this isn't a problem we'd need to worry about. Until it is... ??

I'm working on a list of serverless enterprise applications (whether open source, open core, or just old-fashioned pay-us-now enterprise), and to be honest, I only know of two so far: - https://github.com/webiny/webiny-js - https://github.com/formkiq/formkiq-core (the project I work on) Does anyone know of any more? What I'm looking for is an enterprise software solution (CMS, DMS, CRM, ERP, etc.) that customers would deploy and host in their cloud account. I feel like this is the future of software, but maybe that future is still a ways off. Thanks!

We (my cofounder and I) have built a lot of custom applications over the years. We found that this process was always the same. 1) Collect data from users and create a place to store it in (database, filesystem, etc) 2) Organize the data we've collected, so you can find it later 3) Process the data we've collected. Processing could include transforming the data, performing an action or sending the data to another system This led us to create FormKiQ. FormKiQ is a platform application that gives developers 100% control of their data, letting them automatically perform actions on the data through an event messaging architecture. We’ve built FormKiQ with AWS Serverless Application Model (SAM), using AWS Lambda, API Gateway, and DynamoDB. The reason for this is that we wanted a system that didn’t require any configuring and managing of server