Free Cloud Bill Analysis

What this page is, and what it is not

A bill-analysis page that promises a sample PDF, a same-day SLA, and a certificate wall is selling a product this form does not run. This one describes the live path.

The live path is a form. You answer a few spend questions, optionally, so the wizard can show an indicative range. You then attach last month's invoice or cost export as PDF or CSV, up to 5 MB, and tick consent. The site posts that file to an email API. The file goes as an attachment to the analysis inbox. The website does not keep it as a downloadable object. If the sending key is not configured, the request is logged and the form still returns success — which is why this page does not pretend every submit is already in a ticket system.

What this page is not: a private object store with a ninety-day lifecycle, an XLSX drop that accepts 20 MB, a published one-business-day clock, or an analytics event on submit. Those belong to later work. Publishing them here as if they were live would be a lie a finance lead would catch on the first send.

TiCON Cloud is an AWS Advanced Tier Partner you can check on AWS Partner Solutions Finder. AWS usage can be invoiced in taka after you buy reseller billing. Azure and Google Cloud bills are in scope for FinOps advice. They are not a second taka-reseller product. Staff certification lists and years on AWS as a partner are unpublished. Typical compute and storage savings of 15-35% and CloudFront up to 40% are AWS figures from the facts file; they are not a quote for the file you upload, and they are not applied to Azure or GCP on this page.

• Talk to an architect without uploading
• Pay AWS in taka
• AWS partner and reseller

How to send a bill

Export last month from the console you already use. Attach it here. The file travels as email, not as a site object.

AWS customers usually send the PDF invoice from the Billing console, or a CSV cost export. Cost and Usage Reports are the detailed AWS export; a one-month CSV or the invoice PDF is enough for a first review. Azure customers usually send a Cost Management export or the invoice PDF. Google Cloud customers usually send a Cloud Billing export or the invoice PDF. This form does not accept XLSX. If the file is larger than 5 MB, email it to moshiur@ticonsys.com instead of forcing the upload.

You do not need a TiCON login. You do need a work email we can reply to, a company name, and consent that we may use the file to prepare the review. A honeypot field drops obvious bots. The form also rate-limits noisy addresses. Neither of those is a security certification.

• Privacy of this site
• AWS pricing in taka (calculator)

What you receive

A written review of the file you sent. This site does not host a sample invoice PDF, and it does not invent three anonymised taka bills.

You receive an email that discusses the line items in the file: where spend sat last month, what looks idle or oversized, and which levers are worth a next conversation. For AWS that often means commitments, rightsizing, scheduling non-production, and storage tiering. For Azure and Google Cloud it is the same class of FinOps advice against the services in that bill — not a rewrite of that spend onto a taka reseller invoice.

A 12-month finance pack, a board slide, and a named savings number you can take to a CFO as a quote are follow-on work. They are not a download sitting on this URL. Sample BDT bills are omitted because the pricing-examples list is empty. If someone asks for a PDF that looks like a finished engagement, the honest answer is: send last month's file; the sample is the review of that file.

The wizard's 'estimated opportunity' is a separate artefact. It applies industry-style levers to the numbers you typed. It is labelled indicative on purpose. Do not paste it into a budget as if an architect had already read the CSV.

• Managed cloud after the review
• Buy a cloud server (order path)

Privacy of the upload

The file is an email attachment. Treat it as a message to the analysis inbox, not as a vault.

The live API reads the upload in memory and sends it with Resend as an attachment to the analysis inbox. Default destination in this codebase is moshiur@ticonsys.com unless the environment names another address. The website does not write the file into its own object store. There is no public URL for the PDF after you submit.

Email is still a copy. The inbox, the sending service, and any device that opens the message hold the bytes until a person deletes them. That is not a published object-store lifecycle, and this page will not describe one. Do not attach a bill that contains secrets you cannot share with the people who will read that inbox — root keys, password dumps, or customer PII that does not belong on an invoice.

Contact details on the form (name, work email, company, optional phone) travel in the same message so we can reply. Processors already named on the privacy page include Resend for email. You can ask for the copies to be deleted by writing to info@ticonsys.com. Retention is 'as long as needed for the review', not a numbered day count invented for this rewrite.

• Privacy policy

Turnaround, tracking, and what is not live

Receipt is not a clock. Analytics on this form are not wired on this page.

When sending is configured, you may get a confirmation email that the file arrived. That email acknowledges receipt. It does not start a published SLA. Numeric hours and a published clock are omitted because the public response matrix is unpublished. If you need a meeting on a date you control, talk to an architect — that path is the contact form, not a promise hiding in this wizard.

Form analytics for this upload are not on this page. There is no billed event name to paste into a tag manager from this rewrite. Submitting still emails the team. Do not wait for a dashboard ping that this URL does not emit.

The comparison below is the honest split between what this form does today and what a later intake might do. The right-hand column is not a roadmap you should treat as shipped.

AWS, Azure and Google Cloud on the same form

One upload. Three clouds. One taka-reseller product, and it is AWS.

Choose the provider in the wizard so the snapshot can pick a sensible set of levers. AWS answers can mention Savings Plans, rightsizing and scheduling. Azure and Google Cloud answers stay in FinOps language for those platforms. The written review follows the file, not the radio button, if they disagree.

After the review, AWS customers who want local billing read Pay AWS in Bangladesh and AWS services. That is reseller invoicing in taka, on Partner Solutions Finder, with production usually in Mumbai or Singapore. Azure and Google Cloud remain architecture and operations. This page does not invent a Microsoft or Google designation, and it does not turn an Azure or GCP invoice into a taka reseller line.

If the estate is already multi-cloud, send the bill that hurts this month. A second export can follow. Do not wait for a unified CSV format this form does not accept.

• Google Cloud architecture
• Azure architecture
• Compare the three clouds

After the review: billing, ops, or a server order

The free review is the start of a conversation. It is not a purchase.

If the leak is on-demand AWS with no local invoice, the next page is Pay AWS in Bangladesh. If the leak is an unowned estate, managed cloud is the ops conversation — coverage is 24×7; minutes stay in the contract, not on this page. If you already know you need a server rather than a bill review, the order path is Buy a cloud server in Bangladesh, which is quote-based and is not a SKU table.

100+ enterprise clients and 200+ projects are company stats from the facts file. They are not a before-and-after for your CSV. Client legal names wait on clearance. Talk to an architect when you want a person on the thread without waiting for the written review.

• Talk to an architect
• Cloud hosting (learn, not order)