CloudInvoice

Service status

Current availability, stated plainly.

This page lists what works in CloudInvoice right now, what is deliberately not configured yet, and what is waiting on something outside the product. 7 of 11 components are operational. It is maintained by hand rather than by an automated monitor, and it says so rather than implying otherwise.

Components

Every part of the product, and where it stands

Core invoicing is operational

Everything needed to create an invoice and get it in front of a client is working. Card payments and email delivery are not configured in this deployment.

Operational
7Operational
Not configured
3Unconfig
Pending
1Pending

Core platform

3 components

  • Web application

    The application container is running and its health endpoint responds successfully.

    Operational

  • Database

    PostgreSQL is reachable from the application and bound to loopback only on the host.

    Operational

  • Password reset

    Requesting a reset link and setting a new password are implemented, using one-time tokens that expire after an hour. Delivery depends on the email provider below, so a link cannot reach an inbox until that is configured.

    Not configured

Invoicing

3 components

  • Invoice creation and editing

    GST calculation for intra-state and inter-state supply, and sequential invoice numbering. A draft can be edited or deleted; once sent, an invoice can be voided so the record and its number are kept rather than removed.

    Operational

  • Client records

    Adding clients and reusing their billing details on later invoices is available.

    Operational

  • Client payment pages

    Private invoice links open for recipients and show the invoice, totals, and amount due.

    Operational

Payments and delivery

4 components

  • UPI QR codes

    A QR code is generated for the amount due once a UPI ID is saved in workspace settings. The payment reaches your UPI ID directly, so you mark it received using Record payment on the invoice.

    Operational

  • Manual payment recording

    UPI, bank transfer, cash, and other payments can be recorded against an invoice with an amount, date, and reference. The invoice balance and status update from the payment records, and an entry can be removed if it was logged in error.

    Operational

  • Card payments

    Stripe Checkout is implemented, but no payment credentials are set in this deployment, so card checkout returns an unavailable response instead of failing silently.

    Not configured

  • Email invoice delivery

    Sending an invoice by email is implemented, but no email provider credentials are set in this deployment.

    Not configured

Network

1 component

  • HTTPS on the custom domain

    The web server configuration is in place and waiting on domain registration to complete before a certificate can be issued.

    Pending

What each state means

Operational
Available to use today
Not configured
Built, but no credentials in this deployment
Pending
Waiting on an external dependency

How to read this page

What this status page does and does not tell you

Maintained by hand, on purpose.

CloudInvoice does not yet run automated uptime monitoring, synthetic checks, or an incident history feed. Rather than publish a dashboard that looks instrumented but is not, this page is updated by the operator when something changes.

This page is also served by the same infrastructure as the rest of the product. If the application is unreachable, this page will most likely be unreachable too. A status page hosted alongside the service it reports on cannot be a reliable outage signal, and treating it as one would be misleading.

“Not configured” describes this deployment, not a missing feature. The code path exists and is exercised; it returns a clear unavailable response until credentials are supplied. See Security for how payment state is verified and Changelog for what has shipped.

Planned

What would make this page trustworthy

01

Independent monitoring

An external check that runs off the application host, so an outage can be detected and reported rather than silently taking this page down with it.

02

A recorded incident history

Dated entries describing what happened, how long it lasted, and what changed afterwards, kept even when the answer is unflattering.

03

A monitored contact channel

A published address that a customer can reach during an incident, and that someone is responsible for reading.

The parts that are ready are ready to use.

Create a workspace, add a client, and send a GST-correct invoice with a private payment page. The components marked operational above are all you need for that.

Get started