Listing Thumbnail

    Speech-to-Text Server Container

     Info
    Sold by: Sigmodata 
    Deployed on AWS
    Free Trial
    Deploy a production-ready, self-hosted speech-to-text server on AWS EC2. Convert audio into accurate text via a web UI, a REST API, or batch folder conversion over S3, authenticated with your own accounts or API tokens. Uses a GPU automatically when present, falls back to CPU otherwise. All processing stays in your AWS account.

    Overview

    Open image

    This product provides a fully self-hosted speech-to-text server packaged as an Amazon Machine Image (AMI) for AWS EC2 and as a container image. The server converts audio files into text and exposes both a web interface and a simple HTTP REST API. All processing occurs within the customer's AWS environment.

    The AMI launches with a guided browser setup wizard over HTTPS (port 443). You confirm ownership with the EC2 instance ID, create an administrator account, pick a certificate option, and select a Whisper model. No SSH or user-data editing is required for credentials. After setup, the admin account can add users and issue API tokens from /admin - no need to share one password for automation. HTTP Basic auth with any account still works. GPU instances (for example g4dn.xlarge) enable CUDA automatically; CPU instances still work.

    The Marketplace container image authenticates with a PASSWORD environment variable over HTTP on port 8080 and auto-detects a CUDA GPU at startup (pass --gpus all to enable it), falling back to CPU otherwise.

    A Batch tab handles whole folders rather than one file at a time. Point it at an S3 bucket from /admin, and it becomes a file browser over that bucket: upload audio, queue transcriptions, and get a sidecar transcript written back beside each source file. Nothing leaves the instance and the bucket stays in your account. Without a bucket configured, any writable directory bind-mounted at /data works the same way.

    Common use cases include call center transcription, media and meeting transcription, bulk back-catalogue conversion, compliance-sensitive audio processing, and private speech analytics pipelines.

    Whisper models base.en is the default and the only model baked into the image, so the server transcribes English out of the box with no download. Sixteen checkpoints are selectable in total - from the Model tab in /admin on the AMI, or by running /app/scripts/download-ggml-model.sh into a mounted /app/models volume and setting WHISPER_MODEL on the container. Models ending in .en are English-only; the rest are multilingual.

    • tiny, tiny.en (39M, ~1 GB VRAM) - the smallest checkpoints; suited to drafts and keyword spotting rather than final transcripts
    • base (74M, ~1 GB VRAM) - small multilingual, fine for short clips
    • base.en (74M, ~1 GB VRAM) - the default; good English accuracy, small footprint, and the only model that needs no download
    • small, small.en (244M, ~2 GB VRAM) - noticeably better than base
    • small.en-tdrz (244M, ~2 GB VRAM) - small.en with tinydiarize speaker turns; required for the Diarize option in the UI
    • medium, medium.en (769M, ~5 GB VRAM) - strong accuracy, needs a full GPU
    • large-v1, large-v2, large-v3 (1550M, ~10 GB VRAM) - the full-size checkpoints; the largest and slowest of the set
    • large-v2-q5_0, large-v3-q5_0 (1550M quantized, ~6 GB VRAM) - most of the quality at roughly half the disk and VRAM
    • large-v3-turbo (809M, ~6 GB VRAM) - close to large-v3 quality at roughly half the parameters
    • large-v3-turbo-q5_0 (809M quantized, ~4 GB VRAM) - turbo quality on smaller GPUs

    Selecting any model other than base.en downloads it from huggingface.co, so the instance or container needs outbound internet access at that point. Transcription itself never sends audio anywhere.

    Highlights

    • Transcribe calls, meetings, and media in your VPC - audio never leaves your AWS account
    • Add users and revocable API tokens from /admin - not one shared password like most AMI listings
    • HTTPS wizard, automatic GPU or CPU, and a Batch tab for whole S3 folders

    Details

    Delivery method

    Supported services

    Delivery option
    Deploy as container

    Latest version

    Operating system
    Linux

    Deployed on AWS
    New

    Introducing multi-product solutions

    You can now purchase comprehensive solutions tailored to use cases and industries.

    Multi-product solutions

    Features and programs

    Financing for AWS Marketplace purchases

    AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
    Financing for AWS Marketplace purchases

    Pricing

    Free trial

    Try this product free for 5 days according to the free trial terms set by the vendor. Usage-based pricing is in effect for usage beyond the free trial terms. Your free trial gets automatically converted to a paid subscription when the trial ends, but may be canceled any time before that.

    Speech-to-Text Server Container

     Info
    Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
    Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator  to estimate your infrastructure costs.

    Usage costs (1)

     Info
    Dimension
    Description
    Cost/unit/hour
    Hours
    Container Hours
    $0.08

    AI Insights

     Info

    Dimensions summary

    You pay by container hours, billed for each hour the container runs in your AWS account. This is usage-based pricing with a single dimension, so your cost scales with runtime rather than with fixed tiers or seats. There are no separate plan levels or feature bundles to choose from. The container detects a CUDA GPU at startup and otherwise runs on CPU, but this does not change the hourly rate. You control cost by managing how long the container stays running.

    Top-of-mind questions for buyers

    You are billed for each hour the container runs in your AWS account, whether it processes audio or sits idle. The rate stays the same on CPU or GPU instances. To stop charges, stop the container. Partial hours may be metered per AWS conventions.
    No. The container auto-detects a CUDA GPU at startup when you pass --gpus all, and falls back to CPU otherwise. The hourly software rate is the same either way. Your underlying AWS instance cost differs by instance type, but that is separate from this software charge.
    No. Billing is based only on container runtime hours, not on users or tokens. The container authenticates with a PASSWORD environment variable over HTTP on port 8080. Adding automation or connections does not add a per-seat or per-token charge.
    www.sigmodata.com
    Helpful?

    Vendor refund policy

    Refunds are handled in accordance with AWS Marketplace refund policies. Buyers may request a refund within 48 hours of initial purchase or launch if the product does not function as described on supported EC2 instance types. To request a refund or support, contact support@sigmodata.com 

    How can we make this page better?

    Tell us how we can improve this page, or report an issue with this product.
    Tell us how we can improve this page, or report an issue with this product.

    Legal

    Vendor terms and conditions

    Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Usage information

     Info

    Delivery details

    Deploy as container

    Supported services: Learn more 
    • Amazon ECS
    • Amazon EKS
    • Amazon ECS Anywhere
    • Amazon EKS Anywhere
    Container image

    Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.

    Version release notes
    • Built from the CUDA variant of the image with a runtime GPU probe: run with --gpus all to enable CUDA-accelerated transcription; falls back to CPU automatically when no GPU is present. No configuration needed either way.
    • Image is ~2-3 GB larger than the CPU-only 1.x line due to the bundled CUDA runtime.
    • PASSWORD environment variable HTTP Basic auth on port 8080 is unchanged.

    Additional details

    Usage instructions

    This container runs a Speech-to-Text server that auto-detects a CUDA GPU at startup (pass --gpus all to enable it) and falls back to CPU otherwise. Same image either way:

    • Web UI for uploading audio and viewing transcriptions
    • REST API for programmatic access
    • Configurable output formats
    • Batch tab when you bind-mount a folder at /data (upload, queue, sidecar transcripts)
    • /health endpoint for monitoring
    • Optional HTTP Basic auth (PASSWORD env var, username sigmodata)

    Default port: 8080. Image is larger than the 1.x CPU-only line (~2-3 GB extra) because it bundles the CUDA runtime.

    Run on CPU:

    docker run --rm -p 8080:8080 \ -e PASSWORD=your_password \ -v /path/to/audio:/data \ <IMAGE_URI>

    Run with GPU acceleration (requires the NVIDIA Container Toolkit on the host):

    docker run --rm --gpus all -p 8080:8080 \ -e PASSWORD=your_password \ -v /path/to/audio:/data \ <IMAGE_URI>

    The Batch tab appears when /data is a writable directory. Omit -v /data if you only need interactive /inference.

    For full usage documentation and examples, visit: https://www.sigmodata.com/products?product=speech-to-text-server#speech-to-text-server 

    Where your data is stored

    • Audio you mount at /data and the transcripts written beside it are stored in that bind mount only, on storage you control. The container writes nothing outside /data.
    • The PASSWORD environment variable is read at startup and is not written to disk by the container.
    • The container keeps no other state; it is safe to run with a read-only root filesystem apart from /data.

    Encryption

    • In transit: the container serves plain HTTP on port 8080. Terminate TLS in front of it (an Application Load Balancer, a service mesh, or an ingress controller) before exposing it outside your VPC.
    • At rest: encryption of the /data volume is controlled by the storage you attach (EBS, EFS, or FSx encryption), not by the container.

    Rotation

    • Rotate the PASSWORD value by updating the environment variable in your task definition, Kubernetes secret, or compose file and redeploying. Store it in AWS Secrets Manager or SSM Parameter Store rather than in plain text.

    Checking that the product is healthy

    1. Request GET http://<host>:8080/health, which returns the service state.
    2. Use it as the ECS container health check or the Kubernetes liveness and readiness probe.
    3. Inspect logs with docker logs, kubectl logs, or the awslogs driver.

    Backup and recovery

    • The container is stateless. Back up the volume you mount at /data with your normal snapshot or replication process, and redeploy the image to recover.

    Service quotas and cost

    • GPU tasks need GPU-capable instances in your ECS or EKS cluster, which draw on the "Running On-Demand G and VT instances" vCPU quota. That quota is 0 on a new AWS account. Request an increase in Service Quotas -> Amazon EC2.
    • You pay the AWS Marketplace charge for this product plus the AWS resources it uses: ECS or EKS compute, storage for /data, and data transfer out.

    Support

    Vendor support

    Support contact: Email: aws-support@sigmodata.com  Support URL: https://www.sigmodata.com/contact 

    Support description: Email aws-support@sigmodata.com  or https://www.sigmodata.com/contact . We help with AMI launch, the HTTPS wizard, GPU or CPU operation, the web UI, REST API, and batch transcription. We reply within one business day, Monday through Friday, US Pacific time.

    AWS infrastructure support

    AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

    Similar products

    Customer reviews

    Ratings and reviews

     Info
    0 ratings
    5 star
    4 star
    3 star
    2 star
    1 star
    0%
    0%
    0%
    0%
    0%
    0 reviews
    No customer reviews yet
    Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.