Estoril Ambiental: the corporate website and a web system built to measure

A system designed around the way the company works, with role-based access, field records in photo and video and documents issued by the system itself — and the infrastructure on AWS under our management.

🧩 a custom web system, built from scratch
📸 field records with photo and video
☁️ AWS infrastructure under our management

The client

Estoril Ambiental, based in Atibaia (São Paulo), has worked in recyclable waste management for companies since 2009. It is a sector where the service has to come with a document: whoever hires it needs to prove where the material ended up. That requirement — not a list of features — is what defined what the system had to be.

What the project called for

What the company does is physical; what it has to hand over is a document. The system had to cover both.

👥

One record, several teams

Different teams work on the same record at different moments. The system has to give each one the screen for its role, without opening up what is not theirs.

📄

The document has to come from the system

In a sector where the service is proven by a document, the paper issued at the end only holds up if the system itself is the source of what it states.

📱

The record happens away from the office

Part of what matters is captured in the field. The system has to accept photos, videos and files at the moment and in the place where the service is delivered — straight from a phone.

🔑

Outside companies use it too

External partners need their own access, limited to what concerns them — which changes the permission design of the whole system.

What we built

A corporate website and a web system built to measure for the company.

🌐

Corporate website

Company presentation, one page per service front, contact, a partner showcase and the privacy and consent pages, with a cookie notice.

🧩

A custom web system

No off-the-shelf package bent into shape: the screens, the records and the documents were designed around the way the company already works, not the other way round.

🔐

Role-based access

Each team signs in with its own access and sees the screens for its role, all tied to the same central record — each with what belongs to it.

📸

Field records with photo and video

The crew records photos and videos straight from a phone, and the file stays attached to the service record, at the moment the service happens.

📄

PDF documents and reports

The documents and reports the company needs to print, file or send come ready out of the system, built from what is already recorded.

🤝

Partner area

Partner companies sign in through their own access, limited to what concerns them.

☁️

Files and infrastructure on AWS

Photos, videos and documents live on Amazon S3, the database runs on RDS and Cloudflare answers in front as proxy, firewall, CDN and cache. The whole infrastructure is looked after by us.

🛡️

Environment under continuous management

Beyond hosting, we watch: platform updates, fixes for disclosed vulnerabilities and periodic environment reviews are part of the contract, not of a separate project.

What is live

The fronts we delivered and keep running.

Corporate website Custom web system Role-based access Records with photo and video PDF documents Partner area Files on S3 Cloudflare Security management

What it changes in practice

The effect of having the record and the document in the same place.

1

The document comes out of the system

What the company hands to its own customer is generated by the system itself, from what was recorded along the way.

2

Each team on its own screen

Role-based access separates what each team sees and does, without anyone having to work around the system.

3

The record stays with the service

Photos, videos and files stay attached to the record and remain there afterwards, whenever someone needs to look.

4

Infrastructure and maintenance under contract

Servers, database and files on Amazon AWS, with Cloudflare as proxy, firewall, CDN and cache: the people who look after the code look after the environment.

This case study describes our work: what we built, with what technology and what we keep running. How the client's operation works internally is theirs — it is not put on display here.

Does your operation need to prove what it did, not just do it?

Records in the field, documents coming out of the system and each team on its own screen. Tell us what your operation needs.