What do you use today instead of Stigg (https://www.stigg.io/stigg-for-developers) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Stigg better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

Sean Romagueraneutral

Currently, we track prompt and token usage directly in Postgres. We also have custom logic for feature gating and piping billing events to Stripe. Honestly, building and maintaining that ourselves is a significant effort. Stigg appears to abstract a lot of that complexity away, especially the real-time enforcement and credit management, which could save us considerable development and operational overhead. The integration with our existing Stripe setup is a plus. However, I'd need to understand the implementation details for BYOC (Bring Your Own Cloud) and how much control we truly retain over data ownership and the underlying infrastructure. Without that clarity, it's hard to say if it's better or worse. The cost is also a factor; we're a small startup, so any new tooling needs to be cost-effective. We're using spreadsheets and manual checks for some very early-stage, low-volume features, but for our core product, it's all custom code. I would be willing to pay up to $500 per month, billed monthly.

Simulated interest: 60/100

Renee Reichelneutral

Currently, we're managing our usage and entitlements through a rather manual combination of spreadsheets, Slack approvals, and Stripe records. It's functional for our current seven-person team, but it's becoming increasingly cumbersome. Stigg's promise of real-time enforcement and automated entitlement checks sounds compelling, especially the potential to move away from manual reconciliation. However, the page doesn't clearly detail pricing tiers or how it integrates specifically with our existing Stripe setup beyond mentioning it generally. I'd need to understand the cost structure and see a clearer integration path before committing. Given the complexity and the fact we're prioritizing billing infrastructure hardening, I'm hesitant to adopt a new tool right now unless it's exceptionally straightforward and cost-effective. I would consider paying up to $500 per month, but only if it significantly reduces our operational overhead and scales easily with our growth.

Simulated interest: 40/100

Shiv Panickerneutral

Right now, we're managing token-based limits directly in our code and sending usage events to Postgres. It's functional, but integrating something like Stigg could potentially streamline things, especially with managing entitlements and metering for our new AI document assistant. The promise of real-time enforcement and reducing custom code is appealing. However, I'd need to understand how it integrates with Chargebee, as that's where we handle our subscription tiers. Also, the concept of 'BYOC' and 'BYODB' sounds interesting for data ownership, but I'm not entirely clear on the setup complexity. If it simplifies our current manual checks and provides better scalability without significant engineering overhead, it could be worth exploring. I would be willing to pay up to $150 per month.

Simulated interest: 50/100

Jette Erdmannneutral

Currently, we are using Lago for our usage metering and entitlement rules. Compared to that, Stigg's promise of real-time enforcement and credit management sounds interesting, particularly the "financial-grade credit infrastructure" aspect. However, I would need to understand how it integrates with our existing billing systems and data ownership policies. Our current setup is quite tailored, and the complexity of migrating or integrating such a core component is a significant consideration. The fact that Stigg can "augment, don't replace" and "layer on top of your current billing provider" is appealing, but I'm concerned about the operational overhead and the potential for unforeseen issues during integration. I would need to see more detailed documentation on the BYOC (Bring Your Own Cloud) deployment and how it interacts with our data warehousing. The pricing isn't clear from the page; I'd need to see details on their monthly subscription cost based on usage or features.

Simulated interest: 40/100

Lamar Littelneutral

Currently, my engineering team and I handle usage counting directly within our application code and verify exports using SQL and spreadsheets. It's a meticulous process, but as we grow, it's becoming increasingly time-consuming and prone to errors. Stigg's promise of real-time metering and entitlement management is appealing because it could automate these tasks and provide more granular data, which would be a significant improvement. However, I'm concerned about the complexity of integration and how it might impact our existing infrastructure and costs. I would need to understand how it fits into our current setup and the total cost of ownership. Right now, I'm not willing to pay for such a solution, so the maximum I would pay per month is $0.

Simulated interest: 40/100

Caroline Dufourneutral

Currently, my team and I rely on a shared spreadsheet and manual checks of usage exports to manage plan rules, feature access, and invoicing. It's functional, but cumbersome and time-consuming. Stigg's promise of an integrated API for real-time metering and entitlements is appealing, especially the idea of automating these processes and reducing the friction in our billing. The "runtime enforcement, locally executed" with <10ms p99 response time is impressive. However, I'd need to understand how it integrates with our existing workflow, particularly our invoicing, and what the implementation effort looks like for a small team. The BYOC (Bring Your Own Cloud) option is interesting for data ownership, but I'd need more clarity on the associated infrastructure costs and management overhead. I can't estimate a price without more details on their pricing structure beyond the general subscription model. If it could truly streamline our operations and free up engineering time, I might consider it, but the current manual system, while inefficient, is free.

Simulated interest: 30/100

Geoffrey Walterneutral

Right then, at the moment, we're mostly relying on Stripe for our subscriptions and then a bit of manual admin toggling for specific customer access rules, which is becoming a bit of a headache. The idea of a unified API for pricing, packaging, and billing, especially with the AI features we've just added, sounds promising. Stigg's real-time entitlement checks and metering seem like they'd be a significant improvement over our current setup, potentially saving a lot of engineering time spent on custom logic. The ability to manage AI credits and usage control is particularly relevant given our recent feature additions. However, I'd need to see more about how it integrates with our existing Stripe Billing and how complex the setup actually is. I'm not entirely clear on the pricing structure – it mentions USD per month subscription, but without specific tiers or usage-based breakdowns, it's hard to gauge. If it genuinely simplifies our entitlement management and offers robust AI usage control, I might consider something in the region of $150 per month, but that would be on the higher end for us.

Simulated interest: 70/100

Herman Mierzejewskineutral

We currently use OpenMeter for collecting usage events and capping free-tier consumption for our API product. OpenMeter handles our needs for event ingestion and basic rate limiting. Stigg's focus on AI-specific usage, credits, and real-time enforcement, especially with its promise of p99 latency under 10ms, is interesting. However, the primary difference for us would be how seamlessly it integrates with our existing OpenMeter setup and if it offers a more granular entitlement management than what we've already built. The 'Install with AI' and 'Talk to a Human' options are noted, but without clear pricing information, it's difficult to assess its value proposition against our current solution. I wouldn't pay for Stigg at this time, as our existing solution meets our current needs, and the additional benefits of Stigg are not yet clearly defined for our specific use case.

Simulated interest: 20/100

Jane O'Connerneutral

Currently, I'm manually managing feature access and usage reports using a combination of HubSpot, Stripe, and internal spreadsheets. It's quite time-consuming and prone to errors. Stigg's promise of real-time metering and entitlement checks is appealing, as it could automate a lot of what I do by hand. However, I'd be concerned about the integration complexity and how seamlessly it would work with our existing Stripe billing. The biggest draw would be saving engineering time and reducing manual reconciliation. I'd need to understand the setup process and any potential hidden costs before committing. My maximum would be $300 per month.

Simulated interest: 65/100

Bhuvaneshwar Dubashineutral

Right now, we're using a mix of custom scripts and SQL views to manage entitlements for our three pricing tiers. It's becoming a real bottleneck as we grow, and frankly, it's prone to errors. What makes Stigg potentially better is the promise of a unified API for entitlements and real-time checks. It seems like it could automate a lot of what we do manually. On the flip side, I'd be concerned about the integration effort and how well it fits with our existing backend. We're a small team, so complexity is a big hurdle. I'd need to see clear benefits in terms of time saved and reduced errors to justify switching from our current, albeit imperfect, system. The BYOC (Bring Your Own Cloud) option is interesting, as data ownership is important to us. I'd be willing to pay up to $200 per month for a solution like this, depending heavily on the feature set and ease of integration.

Simulated interest: 70/100