What would stop you from trying Myjson (https://myjson.online/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

Emanuel Rolfsonneutral

I'm hesitant to try Myjson this month primarily because our current hosted JSON database, while not perfect, is a known quantity that handles our versioning and customer-specific settings. We've built scripts around it, and switching would involve a significant migration effort. The version control here is limited to 10 versions, which might not be enough for our needs, and the pay-as-you-go model, while transparent, requires careful monitoring to avoid unexpected costs as we scale. We're currently paying a fixed monthly fee for our existing solution. For Myjson, I'd consider a plan around $50 USD per month, assuming it meets our full requirements.

Simulated interest: 40/100

Anne Buckridgeneutral

The main thing stopping me is the current reliance on Google Sheets and scripts. I've spent so much time documenting our processes to prepare for future automation, and I'm wary of adding another layer without understanding how it integrates. The 'pay-as-you-go' model is interesting, but it's unclear how many API calls our current workflow would generate. Without a clearer picture of usage and how it fits into our existing data pipeline, I can't commit to anything. I'd be hesitant to pay more than $0 per month until I've thoroughly tested it and understood the long-term implications.

Simulated interest: 30/100

Indra Patelnegative

The main thing stopping me is our current process, while manual, is functioning for us right now. We manage shipping rules and customer data in spreadsheets and JSON files, and I'm hesitant to introduce another dependency unless it's absolutely critical and cost-effective. I'm trying to keep costs extremely low. The pay-as-you-go model with 100,000 credits for $25 USD is interesting, but I'd need to understand how many credits we'd actually use. Honestly, I'd probably pay $0 for now, given our budget constraints and the fact our current system, while clunky, works.

Simulated interest: 10/100

Lea Kochanneutral

My current setup uses a paid cloud datastore, mirrored in Git, for our device profiles and rollout configurations. The main hurdle to trying Myjson this month would be the integration effort and ensuring it meets our specific audit trail and versioning requirements, especially since our current solution is well-established. I'd need to assess if the versioning capability, which seems limited to 10 versions, is sufficient for our long-term needs. If the pay-as-you-go model works out to be more cost-effective than our current solution, I might consider it. The advertised pricing starts at $9 for 25,000 credits, which translates to about $25 for 100,000 credits, a comparable cost to what we might be paying now, depending on our usage. I would be willing to pay up to $30 per month if it proves to be a more efficient and reliable solution.

Simulated interest: 50/100

Randy Wolffneutral

Honestly, the biggest thing stopping me is the manual version checking we do now with Airtable and spreadsheets. It's tedious and I'm worried about introducing something new that might complicate our workflow, even if it's just for JSON fixtures. The "pay-as-you-go from $9" sounds promising, but I'd need to see how many credits that actually covers for our typical usage. We're trying to keep costs down, so a clear understanding of that credit system is key. If it fits our needs without a huge commitment, I'd consider paying around $20-25 USD per month, depending on the usage limits.

Simulated interest: 50/100

Flora Watsicaneutral

My current workflow involves exporting JSON data from Airtable for engineering release checks. While Myjson offers automated version control, which is appealing, the primary concern is integrating a new system. We'd need to ensure it seamlessly fits into our existing processes without introducing new points of failure. The pay-as-you-go model is interesting, but I'd need to understand our typical monthly API call volume to estimate costs. I'm currently paying for Airtable, and I'm cautious about adding more tools without a clear benefit. I'd be willing to consider a budget of around $25 per month, but that's contingent on usage and proving value.

Simulated interest: 60/100

Everett Vonneutral

Right now, the main thing stopping me is that our current system, while clunky, is deeply integrated into our Git repository and plain text files. We've built up a process around that, and switching requires a significant effort to refactor and retrain. I'm also a bit hesitant about the versioning limit of '10 version' as mentioned in your description; I need to understand if that's a hard limit or if it can be increased. From a practical standpoint, I'd need to see how this handles complex, nested JSON structures and if it integrates smoothly with our existing workflow. Given our needs, I'd be willing to pay around $25 per month for a service like this if it proves reliable and scalable for our use case.

Simulated interest: 60/100

Rosalie Lucasneutral

This month, what would stop me is the need to fully integrate and test a new system. Today, we manage JSON data across Firebase and spreadsheets, with changes tracked inconsistently through console history and pull requests. While your pay-as-you-go model is attractive, the "10 version" limit on version control is a concern for our compliance needs, and I'd need to understand its implications. If it proved robust enough, I might consider paying around $25 per month for 100,000 credits.

Simulated interest: 40/100

Gudakesa Mishraneutral

Currently, my team relies on Google Sheets and manually updated documents for our JSON templates and webhook samples. The primary concern with adopting a new tool like Myjson would be the integration effort and ensuring it aligns with our existing workflows without disrupting customer onboarding. We've just standardized our templates after a significant effort, so introducing something new requires careful evaluation. From a cost perspective, the pay-as-you-go model is interesting, but without a clear understanding of our API call volume, it's hard to estimate. If we were to consider it, I'd be looking at a budget of around $15 USD per month for initial testing and a small-scale implementation, understanding that this is a very preliminary figure.

Simulated interest: 40/100

Diana Koningneutral

What would stop me? Well, the biggest hurdle is that we currently manage our JSON data in spreadsheets. While it's manual, it's a process we know and it's integrated into our workflow. Introducing a new API-based system means a learning curve for the team and potentially rewriting parts of how we handle client data. I'd need to see how it integrates with our existing spreadsheet-based processes or if it requires a complete overhaul. Honestly, the 'pay-as-you-go from $9' is a bit vague for me. I'd need more clarity on what 'credits' mean in terms of API calls relevant to our typical payload size and frequency. Without that, it's hard to estimate cost. For now, I wouldn't pay anything until I understand the usage model better. Perhaps $10 per month would be a starting point if the usage fits our needs.

Simulated interest: 40/100