Permission-based communication
We send to people who signed up, hold an account, or asked to hear from us. Nothing else.
Digital infrastructure & software
Reliable infrastructure for modern digital communication.
Astravix builds practical software and communication infrastructure for businesses that need dependable, secure and predictable email delivery.
message path
-
Application
Event: user requests password reset event -
Astravix
Templating, suppression check, signing process -
Email Infrastructure
Authenticated delivery over TLS send -
Recipients
People who expect the message deliver
SECURE COMMUNICATION
TRANSACTIONAL EMAIL
RELIABLE INFRASTRUCTURE
SOFTWARE SYSTEMS
OPERATIONAL EMAIL
ASTRAVIX
Our approach
Built around reliability, not volume.
Astravix focuses on controlled, permission-based communication infrastructure. Our systems are designed around predictable sending patterns, domain authentication, reputation management and operational visibility.
Authenticated sending
Messages are sent from domains we control, with standard authentication so receivers can verify the sender.
Reputation-aware infrastructure
Sending is structured so that one type of traffic does not put the reputation of another at risk.
Operational monitoring
Bounces, complaints and delivery events are tracked and acted on, not left in a log.
What we build
Software and the systems behind it.
Astravix builds software products and the communication layer they rely on. Most of our work is not visible to end users. It is the part that makes sure a sign-up confirmation or a security alert arrives when it should.
Transactional messaging
An email layer for applications: templates, event-triggered sending, suppression checks and delivery tracking.
Notification services
Account, security and service notifications, routed by type so each category can be managed on its own.
Software products
Practical web applications and internal tools for everyday business operations, built to be maintained.
Infrastructure
Email infrastructure designed for separation and control.
Astravix uses Amazon SES as an email delivery infrastructure layer for application and business communications. For workloads that require isolated sender reputation and predictable infrastructure, Astravix is seeking two Standard Dedicated IP addresses.
Applications never send mail directly. Every message passes through the Astravix layer first, where it is checked against suppression lists, authenticated, and tagged by workload before it is handed to Amazon SES.
- One entry point for all outgoing application email
- Workloads separated by message type
- Bounce and complaint events fed back into suppression
ASTRAVIX APPLICATIONSProducts and internal services
AUTHENTICATED EMAILSPF · DKIM · DMARC-aligned domains
AMAZON SESEmail delivery layer
STANDARD DEDICATED IP POOLRequested
Dedicated IP 1requested
Dedicated IP 2requested
RECIPIENT MAILBOXESUsers and customers who expect the message
Requested capacity:2 Standard Dedicated IP addresses
Dedicated IP allocation is subject to Amazon SES approval and AWS service requirements.
Astravix is requesting two Standard Dedicated IP addresses for Amazon SES to maintain isolated sending reputation and predictable email infrastructure for its business communication.
Dedicated sending
Why Astravix needs two dedicated IPs
On shared Amazon SES addresses, sender reputation is also shaped by other senders. Dedicated addresses are used only by Astravix, so their reputation reflects our own sending and nothing else. Two addresses in one pool avoid depending on a single IP.
Reputation Isolation
Separating sending infrastructure gives Astravix greater control over sender reputation and allows different communication workloads to be managed independently.
Operational Resilience
Two dedicated IPs provide a more structured sending architecture and allow traffic to be distributed across a dedicated pool.
Predictable Infrastructure
Standard dedicated IPs provide known, stable sending addresses that can be monitored and managed as part of Astravix's email infrastructure.
Operating plan
How the dedicated IPs will be operated.
If the request is approved, this is how Astravix intends to run the dedicated pool. The same rules already apply to our current sending.
-
01
Recipients come from real sign-ups
Addresses are collected only when someone creates an account, requests a service or subscribes. New sign-ups confirm their address before receiving anything else. We do not buy, rent, scrape or share lists.
-
02
Traffic is routed by message type
SES configuration sets assign each type of message to the dedicated pool, so it is always clear which traffic uses which addresses and how each type is performing.
-
03
New IPs are warmed up gradually
Volume on new addresses is increased step by step, starting with the most engaged recipients, using the Amazon SES warm-up process. We do not move full volume onto a new IP at once.
-
04
Bounces and complaints are handled automatically
SES bounce, complaint and delivery events are processed as they arrive. Hard bounces and complaints are added to the suppression list and are not mailed again.
-
05
Unsubscribing is easy
Every non-essential message includes a visible unsubscribe link and a List-Unsubscribe header. Requests are honoured without asking the recipient to sign in.
-
06
Sending pauses when metrics move
Internal alerts are set well below the bounce and complaint rates at which Amazon SES reviews an account. If a rate rises, the affected sending is paused and the cause is found before it resumes.
| Message | Triggered by | Why the recipient gets it | Unsubscribe |
|---|---|---|---|
| Account verification | Sign-up | Requested by the recipient | Not applicable (one-time) |
| Password reset | Reset request | Requested by the recipient | Not applicable (one-time) |
| Security notification | Login or account change | Protects the recipient's account | Not applicable (required) |
| Transactional message | User activity | Direct result of an action they took | Not applicable |
| Service notification | Product or service change | Existing user or customer | Yes, where not essential |
| Business communication | Scheduled | Opted in or existing customer | Yes, in every message |
Use cases
Where Astravix uses email
Every message has a reason to exist and a recipient who expects it. Most are triggered by something the recipient just did.
Account verification
Email verification and account activation.
Password & security
Password resets and security notifications.
Transactional messages
Application-generated messages triggered by user activity.
Service notifications
Operational updates and important product notifications.
Business communication
Permission-based communication with existing users and customers.
System alerts
Important infrastructure and application notifications.
What we do not send
- Mail to purchased lists
- Unsolicited bulk email
- Spam
- Deceptive email
- Misleading content
Sending practices
Responsible sending is part of our infrastructure.
Astravix is committed to maintaining clean sending practices and protecting the reputation of its email infrastructure. Recipients are expected to have a legitimate relationship with the service or have provided appropriate permission to receive communication.
Hard bounces and complaints lead to suppression. Addresses that stop engaging are reviewed. New sending is increased gradually rather than all at once.
- Permission-based recipients
- Domain authentication
- SPF / DKIM / DMARC configuration
- Bounce monitoring
- Complaint monitoring
- Suppression handling
- List hygiene
- Controlled sending patterns
- Reputation monitoring
Domain & security
Built with authentication in mind.
Astravix uses standard email authentication and transport security practices to establish domain identity and protect communications.
Declares which servers are allowed to send mail for a domain.
Adds a cryptographic signature so receivers can confirm a message was not altered.
Tells receivers how to handle mail that fails SPF or DKIM checks, and where to send reports.
Encrypts messages in transit between mail servers where supported.
Protects traffic between visitors and Astravix web services.
Company
About Astravix
Astravix is a technology-focused business building practical digital products and infrastructure. Our focus is on creating reliable systems that businesses can depend on for everyday digital operations.
We prefer small, well-understood systems over large, clever ones. We write things down, monitor what we run, and answer our email.
- Company contact
- contact@astravix.web.id
- Website
- astravix.web.id
Principles
How we work
Reliability
Systems should behave predictably.
Transparency
Clear infrastructure and responsible communication.
Security
Authentication and operational controls matter.
Simplicity
Technology should solve problems without unnecessary complexity.
Contact
Let's build reliable communication infrastructure.
For business inquiries, infrastructure questions, or partnership opportunities, contact Astravix.
contact@astravix.web.idTo report a message you believe was sent in error from an Astravix domain, write to the same address. Include the message headers if you can.