Website
1mpulso
My own studio, building websites for freelancers and small businesses on a subscription basis. Static sites with security headers and a restrictive content policy, no third-party trackers, and deployments that roll back in one click. The client never has to learn any of it.
Why the code is not here
The studio's code and its client sites are not public.
Why it exists
A freelancer or a five-person company that needs a website has two bad options. A subscription site-builder template, which loads in five seconds, ships six third-party trackers and looks like ten thousand others. Or an agency, which charges up front, delivers, and disappears when a phone number needs changing.
1mpulso does the same thing on a subscription: the site, the domain, the certificates, the changes and the maintenance. The client learns nothing and touches nothing.
The security side
This is where it crosses over into cybersecurity, and not by putting a padlock in the footer.
The sites are static, so there is no database to inject and no admin panel to attack. They ship with security headers and a restrictive content policy whose list of allowed origins is, in practice, the domain itself. No third-party trackers, which besides leaking visitor data are somebody else’s code running on my client’s site.
Dependencies are kept current automatically, with vulnerability analysis on every change. Deployments are atomic and roll back in one click, so a typo in a price is fixed in thirty seconds.
The client asks for none of this because they do not know it exists, and it is what separates a site that lasts five years from one that gives you a bad day.
How I work there
Each client is their own repository, with their own working branch and their own preview before anything touches production. I validate changes there and never on the live site.
There is a method file shared across all the projects, with the conventions and with the list of mistakes not to repeat. That list is worth more than any template, and it grew from getting things wrong.
Working with agents
A one-person studio with two clients on maintenance needs the repetitive part not to eat the time. AI agents do that work against the method file: writing a blog entry with the schema the build validates, processing images, reviewing dependencies.
What I do not delegate is anything visible. Every change goes through the preview and I validate it myself before it reaches the site of a client who pays.
Status
Two clients in production, one of them a building refurbishment company in Madrid still on maintenance. The studio code and the client sites are not public.