Our Terms: We make it simple to use Devii

Got a niche need? Talk to me.

Anthony Molzahn

CEO and Co-Founder

See More in the FAQ

The TL;DR Version

You get (roughly) the equivalent compute power of an AWS EC2 small instance. For 98% of users, this is more than enough to build, test, and run production GraphQL APIs. If you're in the 2% who need more (and we love power users!), we'll work with you to find a solution that makes sense.

What Does Your Monthly Allocation Include?

Unlimited Database Connections

Connect to as many SQL databases as you need. Whether it’s 1 database or 50, we don’t count connections—we count the work your APIs actually do.

Query-Based Resource Usage

Your monthly allocation is based on computational complexity, not arbitrary limits. Think of it like a monthly “compute budget” that refreshes every billing cycle.

Automatic Schema Updates

Database schema changes, new table additions, column modifications; all handled automatically without counting against your usage limits.

Understanding Query Complexity

Not all GraphQL queries are created equal. Here’s how to think about your usage:

Simple Queries (Low Impact)

				
					query {
  users {
    id
    name
    email
  }
}
				
			
  • What it does: Fetches basic fields from one table
  • Compute cost: Minimal (like loading a simple webpage)
  • Typical usage: User profiles, basic listings, simple lookups

Medium Queries (Moderate Impact)

				
					query {
  users {
    id
    name
    posts {
      title
      createdAt
      commentCount
    }
  }
}
				
			
  • What it does: Joins across 2-3 tables with basic aggregations
  • Compute cost: Moderate (like loading a dashboard with charts)
  • Typical usage: Content feeds, reporting dashboards, related data

Complex Queries (Higher Impact)

				
					query {
  users {
    id
    name
    posts {
      title
      comments {
        content
        author {
          name
          profile {
            avatar
            bio
          }
        }
      }
      tags {
        name
        relatedPosts {
          title
        }
      }
    }
  }
}
				
			
  • What it does: Deep nested relationships, multiple joins, heavy aggregations
  • Compute cost: High (like generating a complex analytics report)
  • Typical usage: Comprehensive APIs, data analytics, AI training queries

Real-World Usage Examples

Light User Profile

Typical Application: Simple mobile app, basic web dashboard

  • ~10,000 simple queries per month
  • ~2,000 medium queries per month
  • ~100 complex queries per month
  • Supports: 500-1,000 daily active users
  • Examples: Personal projects, small business apps, prototypes

Moderate User Profile

Typical Application: Production web application, B2B dashboard

  • ~25,000 simple queries per month
  • ~8,000 medium queries per month
  • ~1,000 complex queries per month
  • Supports: 2,000-5,000 daily active users
  • Examples: SaaS applications, e-commerce sites, content platforms

Power User Profile

Typical Application: High-traffic application, data-intensive platform

  • ~50,000 simple queries per month
  • ~20,000 medium queries per month
  • ~5,000 complex queries per month
  • Supports: 10,000+ daily active users
  • Examples: Social platforms, analytics dashboards, AI-powered applications

What Happens If You Go Over?

We’re Not the Usage Police

We don’t auto-throttle or suspend accounts for usage overages. If you consistently exceed your allocation, here’s what actually happens:

  1. We reach out personally to understand your use case
  2. We explore optimization opportunities (sometimes a query tweak saves 50% compute)
  3. We discuss upgrade options that make sense for your needs
  4. We might ask if you want to pay us more money (novel concept, we know)

Temporary Spikes Are Normal

Going viral? Feature launch causing traffic surge? Data migration running heavy queries? These temporary spikes are totally normal and expected. We’re not going to penalize you for success.


The One Thing We’re Strict About: Account Sharing

Please Don’t Share User Accounts

We’re a small startup, and we respect fellow entrepreneurs. If you need multiple people accessing Devii, please get a team account. Here’s why this matters:

  • Shared accounts create security risks for your data
  • We can’t provide proper support when we don’t know who’s asking
  • It makes our usage analytics meaningless (and we use those to improve the product)
  • Frankly, it hurts our revenue and we’re trying to build a sustainable business

Team Accounts Are Designed for This

  • Proper user management and permissions
  • Individual usage tracking and optimization
  • Better security and audit trails
  • Support tickets that make sense
  • Pricing that scales with actual usage

Our Philosophy on Fair Use

We Want You to Succeed

Your success is our success. We’d rather help you optimize your queries and grow your application than impose arbitrary limits that hurt your business.

Reasonable Use Is Subjective

What’s “reasonable” depends on your application. A social media platform naturally uses more resources than a simple CRUD app. We take context into account when evaluating usage patterns.

Communication Over Restrictions

If there’s ever a usage concern, we’ll talk to you first. Maybe there’s a query optimization opportunity. Maybe you need a different plan. Maybe you’re doing something really cool and we want to learn from it.


Questions About Usage?

We’re here to help you succeed, not to restrict your growth. If you’re unsure about your usage patterns, building something ambitious, or just want to chat about GraphQL optimization, reach out to us.

Remember: We built Devii because we believe GraphQL APIs should be accessible to everyone, from weekend hackers to enterprise architects. These guidelines help us keep the service sustainable while giving you the freedom to build amazing things.

Happy querying!

Got questions? Let's talk!