Frequently asked questions
Who runs this site?
An independent team operates this storefront for the Auralux text-to-speech API. We handle the infrastructure so your development team can focus on conversation design and user experience without worrying about audio generation details.
Are you affiliated with OpenAI?
No. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our API mimics the OpenAI request shape for convenience, but we are a separate entity.
Where are the voices from?
Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. Every generated file also carries an inaudible watermark marking it as synthetic speech.
Do you store my text?
Input text is used only to produce the audio and is not used for training. We keep request metadata like time, character count, and status for billing purposes, but not the raw text itself.
Do you store the audio?
Generated audio is returned in the response and is not stored by us. Only request metadata is retained for billing. We do not keep the audio files after delivery to your application.
How do I contact support?
Support is available by email only. There is no live chat or phone support. You can reach us via the contact page or email link provided on our site for any questions or issues.
Is there a phone number?
No, we do not have a phone number. All support communication happens via email. We prefer written correspondence to ensure clear records and efficient handling of your technical queries or billing questions.
Do you have an SLA?
No, we do not offer an SLA or uptime guarantee. Our service is designed for development teams who understand that cloud APIs may experience variable load. We do not provide enterprise contracts or on-premise installs.
Are you certified?
We do not hold certifications such as SOC 2, HIPAA, or GDPR certificates. We are an independent storefront without formal enterprise compliance certifications. Our data practices are straightforward: text is used only for generation.
Do you have a privacy policy?
Input text is used only to produce the audio and is not used for training. Generated audio is returned in the response and not stored. Request metadata (time, characters, status) is kept for billing.
Can I sue you?
Is the data secure?
We use standard cloud infrastructure for our API. Input text is processed to generate audio and not stored long-term. Request metadata is kept for billing. We do not claim specific security certifications like SOC 2.
Who owns the voices?
Our voices are based on recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain readings. We provide these as presets. The underlying recordings have specific licenses, but we manage the synthesis engine and voice configurations for you.
Is this a startup?
We provide a simple, character-based TTS API designed for development teams building voice-enabled applications.
Who we are
Auralux is an independent storefront for the Auralux text-to-speech API. We focus on the engineering details so your developers can concentrate on conversation design and user experience without getting bogged down in audio infrastructure.
Independent editorial team
We are not a large corporate department.
Developer-focused
We designed the API to match the OpenAI request shape, so your existing SDKs work by simply changing the base URL. We provide clear endpoints for voices and models, making integration straightforward for teams of any size.
- Standard JSON request body
- OpenAI SDK compatible
- Clear character limits
No corporate backing
We do not have a parent company or venture capital funding driving us toward a specific exit. This independence means our pricing and feature roadmap are driven by the needs of our users, not corporate strategy.
Our mission
Auralux exists to remove the friction from adding voice to your applications. We handle the heavy lifting of audio generation, allowing your development team to focus entirely on conversation design and user experience rather than wrestling with complex synthesis pipelines.
Simplify TTS integration
Our API mirrors the familiar OpenAI structure, meaning you can swap in our endpoint with minimal code changes. Send text, receive audio. It’s that straightforward, designed specifically for teams building voice-enabled chatbots and assistants without unnecessary abstraction layers.
Transparent pricing
We charge strictly by character count: $10 per million characters, with failed requests costing nothing. There are no hidden monthly plans, no per-seat fees, and no surprise invoices. You pay only for what you use, starting with a simple $0.50 trial credit for new accounts.
Support for teams
We provide a simple, character-based TTS API designed for development teams building voice-enabled applications. Our infrastructure processes requests sequentially, ensuring clear billing metadata for every character generated. We keep it simple so you can scale your voice features without worrying about complex enterprise contracts.
Voice licensing
Our voices are derived from the LibriTTS-R dataset, ensuring a clear and consistent audio profile. We selected these specific recordings to provide a reliable foundation for our eight distinct voice presets, balancing clarity with natural intonation for voice assistants and chatbots.
LibriTTS-R source
The core audio material comes directly from the LibriTTS-R dataset. This source was chosen for its high-quality, clean speech recordings that translate well into synthetic voice models. It ensures consistency across all generated audio files without the variability of live studio sessions.
CC BY 4.0 license
Voices are based on licensed recordings: LibriTTS-R (CC BY 4.0), from LibriVox public-domain audiobook readings. This allows us to legally use, modify, and distribute the source recordings for commercial and non-commercial purposes. It provides a transparent legal framework for your applications without hidden royalty fees.
LibriVox recordings
The recordings are sourced from LibriVox, a platform dedicated to public-domain audiobooks. These are volunteer readings of classic literature, ensuring the content is free of copyright restrictions.
Data policy
We treat your text as a transient input. The characters you send are used exclusively to generate the audio file returned in the response. We do not use your input data to train our models or improve the underlying engine, ensuring your content remains yours.
Generated audio is returned in the response and not stored. This means your voice outputs are ephemeral, reducing data retention risks for your application’s specific use cases.
Billing metadata only
To manage your account and calculate charges accurately, we retain request metadata. This includes the timestamp, character count, and status of each synthesis job.
This limited data is used solely for billing purposes and is not shared for marketing or analytics. It ensures you see exactly what you paid for without unnecessary data accumulation.
- Timestamp of request
- Character count processed
- Request status (success/failure)

Technical limits
We operate without a formal Service Level Agreement, meaning we do not guarantee specific uptime percentages or response time targets. Our infrastructure is designed for reliability, but it is not backed by enterprise contracts or certified compliance standards like SOC 2 or HIPAA. You should plan your application’s error handling accordingly, as we do not offer SLA credits or on-premise deployment options.
No SLA guarantee
Unlike larger providers, we do not publish a formal SLA document or provide financial credits for downtime. Our focus remains on delivering a straightforward, character-based API without the overhead of enterprise-grade uptime contracts. This keeps our pricing simple and transparent, though it means you assume the risk for minor service interruptions.
- No formal SLA document
- No downtime credits
- No enterprise contracts
No uptime promise
Queue under load
Requests are processed sequentially. If many users generate audio simultaneously, your request may wait in a queue before synthesis begins. Short phrases take a few seconds.
Longer texts: split into parts of up to 4096 characters and join the audio files. While this ensures high-quality output, the cumulative processing time increases with text length. During peak periods, this queueing effect may become more noticeable.
- Sequential processing model
- Latency increases during peak load
- Retry logic recommended
Contact us
Auralux is built by a small, independent editorial team focused on developer needs. We prioritize clear communication over corporate bureaucracy, ensuring that your questions reach the right people quickly without unnecessary layers of management.
Email support only
Our primary support channel is email. We value thoughtful, detailed responses that allow us to address technical specifics accurately. You can reach our team at [email protected] for any integration questions or billing inquiries.
No live chat
We do not offer live chat. While instant messaging can be convenient, we find that email allows for better documentation of issues and reduces the noise of multiple simultaneous conversations. This ensures your support ticket isn't lost in a stream of short messages.
No phone number
There is no phone number to call. We operate asynchronously, which suits development teams across different time zones. Email allows you to attach logs, code snippets, or error details directly to your query, making troubleshooting more efficient than a verbal explanation.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. This model simplifies budgeting for large teams, as expenses are tied strictly to character count rather than unpredictable minute-based tiers.
23 languages
Any voice speaks any of these languages.
