Docs / Billing & Account / Setting Up Automatic Billing Alerts

Setting Up Automatic Billing Alerts

By Admin · Jan 31, 2026 · Updated Apr 24, 2026 · 6 views · 2 min read

In this article, we'll walk through the complete process of working with alerts in a server environment. Understanding notifications is essential for maintaining a reliable and performant infrastructure.

Prerequisites

  • A VPS running Ubuntu 22.04 or later (2GB+ RAM recommended)
  • Current billing email on file
  • Access to your Kazepute account dashboard
  • Root or sudo access to the server

Accessing Billing Settings

The notifications component plays a crucial role in the overall architecture. Understanding how it interacts with alerts will help you make better configuration decisions.


Portal Dashboard → Account → Billing Settings

1. Click "Payment Methods" tab
2. Click "Add Payment Method"
3. Enter your card details
4. Click "Save" to update

This configuration provides a good balance between performance and resource usage. For high-traffic scenarios, you may need to increase the limits further.

  • Test your backup restore procedure monthly
  • Monitor disk space usage and set up alerts
  • Enable automatic security updates for critical patches

Understanding Charges

It's recommended to test this configuration in a staging environment before deploying to production. This helps identify potential compatibility issues and allows you to benchmark performance differences.


Portal Dashboard → Account → Billing Settings

1. Click "Payment Methods" tab
2. Click "Add Payment Method"
3. Enter your card details
4. Click "Save" to update

Each line in the configuration serves a specific purpose. The comments explain the reasoning behind each setting, making it easier to customize for your specific use case.

Performance Considerations

When scaling this setup, consider vertical scaling (adding more RAM/CPU) first, as it's simpler to implement. Horizontal scaling adds complexity but may be necessary for high-traffic applications.

Managing Payment Methods

The default configuration works well for development environments, but production servers require additional tuning. Pay particular attention to connection limits, timeout values, and logging settings.

Performance Considerations

If you encounter issues during setup, check the system logs first. Most problems can be diagnosed by examining the output of journalctl or the application-specific log files in /var/log/.

Conclusion

This guide covered the essential steps for working with alerts on a VPS environment. For more advanced configurations, refer to the official documentation. Don't hesitate to reach out to our support team if you need help with your specific setup.

Was this article helpful?