​

Which to use?

Select the right Antryk service type based on your application’s needs. Each service type is optimized for different use cases and deployment patterns.

​

Quick Decision Guide

​

Detailed Comparison

​

Web Services

Best for:

• Backend APIs and microservices
• Webhooks and real-time processing
• Applications requiring persistent connections
• High-throughput services
• Database connections and connection pooling

Characteristics:

• Continuous operation
• Autoscaling based on CPU/memory
• Health checks and automatic recovery
• Custom domains with SSL
• Environment variables

Example use cases:

• REST API server
• GraphQL endpoint
• Webhook receiver
• Long-running services
• API gateway

Get Started

Deploy a web service

​

Static Sites

Best for:

• Frontend applications
• Marketing and landing pages
• Documentation sites
• JAMstack applications
• Static content with CDN

Characteristics:

• Pre-rendered content
• Global CDN distribution
• SSR and ISR support
• Automatic deployments
• Preview environments

Example use cases:

• React/Vue/Angular app
• Next.js application
• Blog or documentation
• Marketing website
• Portfolio site

Get Started

Deploy a static site

​

Background Workers

Best for:

• Processing message queues
• Async task execution
• Batch operations
• Data synchronization
• Long-running background jobs

Characteristics:

• Queue-based processing
• Auto-scaling workers
• Retry logic and error handling
• Cost-efficient for async workloads
• Monitoring and metrics

Example use cases:

• Email sending
• Image processing
• Payment processing
• Data ETL jobs
• Report generation

Get Started

Deploy a background worker

​

Cron Jobs

Best for:

• Scheduled tasks
• Periodic data operations
• Automated workflows
• Cleanup and maintenance
• Time-based triggers

Characteristics:

• Cron-based scheduling
• Serverless execution
• Pay-per-execution pricing
• Automatic retries
• Execution history

Example use cases:

• Daily database backups
• Periodic data cleanup
• Scheduled reports
• Health checks
• Cache warming

Get Started

Deploy a cron job

​

Serverless Functions

Best for:

• Event-driven workloads
• HTTP endpoints
• Webhook handlers
• Low-traffic APIs
• Cost-optimized services

Characteristics:

• Pay-per-execution pricing
• Auto-scaling from zero
• Event triggers
• Fast cold starts
• Built-in timeout

Example use cases:

• Webhook endpoint
• Form submission handler
• API proxy
• Event processor
• Micro-function

Get Started

Deploy a serverless function

​

Choosing by Use Case

​

Building a Full-Stack Application

Frontend: Static Site
Backend: Web Service
Database: PostgreSQL or MongoDB
Background Jobs: Background Workers
Scheduled Tasks: Cron Jobs

​

API Development

Primary API: Web Service
Webhooks: Serverless Functions
Background Processing: Background Workers
Database: PostgreSQL

​

Content Website

Frontend: Static Site
CMS Backend: Web Service
Storage: Storage Buckets
Database: PostgreSQL or MongoDB

​

Real-Time Processing

Processing Service: Web Service
Queue: Redis
Workers: Background Workers
Monitoring: Metrics & Logs

​

Migration Guide

​

From Heroku

​

From AWS

​

From Vercel

​

Still Unsure?

If you’re not sure which service type to use:

1. Start with Web Services for most backend applications
2. Use Static Sites for frontend deployment
3. Consider your traffic pattern - constant vs. sporadic
4. Think about scaling needs - autoscaling vs. fixed instances
5. Review pricing models - pay-per-second vs. pay-per-execution

Contact Support

Get help choosing the right service