Category: Custom software
Hojarasca Danza: their videos on their own website
Its videos used to depend on third-party platforms and their terms. Now it has its own video platform, and its team manages it.
5 weeks from start to delivery
Custom software
Custom Applications
No off-the-shelf software fits your business perfectly. You need an application that works the way your company works. We develop it to measure, with no servers to maintain. It handles peaks in usage and costs according to how much it is used.
- Meeting and quote
- Design and development
- Delivery in parts
Who it is for
It is for you if…
- Companies without an IT team that want their own application and a provider who takes care of it.
- Companies that need a management application, a customer portal or a site where many people work at the same time. No off-the-shelf product covers this well.
- Teams that already have an application and want to stop maintaining servers and pay only for what they use.
- Businesses that can’t afford for the application to go down during peak usage.
- Companies that want a website or shop built for them, with features a template website doesn’t have.
It is not for you if…
- Those who only need a standard website, with a few pages and a contact form. That is solved with a template website hosted on PF Hosting.
- Those looking for a quick prototype that will later be discarded. We build software to last.
- Those who need a desktop application or a video game.
What you get
- Assessment and design
What the application needs to do, how we are going to build it and why, and the delivery plan.
- The application, in parts
The server that processes the data and the screens your team uses. Each part is delivered working.
- Testing and automatic publishing
Each change is tested before it is published. Publishing every version is automatic.
- Documentation and handover
A user and maintenance manual, the application's diagrams and a session with your team.
How the project starts
We start with a meeting. We want to know what the application needs to do, who is going to use it and what data it handles. Based on that, we propose how to build it and explain it to you in plain language before writing any code. Then we send you the quote.
No servers to maintain
Your application doesn’t rely on a server that someone has to keep an eye on. It runs in the cloud only when someone is using it. If usage goes up, capacity grows on its own. If it goes down, you pay less. Nobody has to scale a server at dawn.
Also, everything needed to deploy the application is defined in files. That way, it can be rebuilt entirely somewhere else if that ever becomes necessary.
Fast and protected from day one
The screens your team uses are served from copies distributed around the world, so they load quickly from anywhere. A filter sits in front and stops attacks before they reach the application. Images are served lightweight and in the format each browser handles best.
What can be built on this foundation
The same foundation is used to build search engines over large catalogues and video sites. It also works for a site that connects those who offer a service with those who need it. It powers order management applications and portals where your customers can view their invoices. And websites and shops built for you, with features a template website doesn’t have. Every project is different. The way of building it is the same.
We deliver in parts
You won’t wait months to see something. We deliver in parts, and every part works. Each change is tested before it goes live. Releasing a new version is automatic.
After delivery
A live application needs someone behind it. We offer maintenance. Your application uses third-party components, such as the browser’s padlock or the database. We keep them up to date, review the costs and monitor that everything works. If you have someone to take it on, they receive the documentation and a meeting to walk them through it.
What we build it with
On the server side, serverless functions on AWS, Amazon’s infrastructure. You pay per use and they grow on their own with demand. The application exposes an API to communicate with the visible part and with other systems. PostgreSQL or Aurora database for relational data, and DynamoDB when the model is simple and the volume is high. All the infrastructure is defined as code: everything needed to set it up, written in files. That way, it can be rebuilt entirely in another account or region. The visible part is built with Vue, React or WordPress depending on the case, and is served through CloudFront with a web application firewall (WAF) in front. Testing and publishing run in a pipeline: the automated process that tests and publishes every change. That pipeline checks third-party components and publishes without fixed access keys.
Glossary
- Serverless
Your application doesn't occupy a server that is permanently switched on. It runs when someone uses it, and you only pay for that usage.
- API
The channel through which two systems exchange data.
- Cloud account
The account, in your company's name, where your application is hosted. You pay per use and you can move it to another provider.
What problems it prevents
What can go wrong and how we prevent it.
- The application going down during peak usage
Capacity grows on its own with usage. No server gets overloaded.
- The cloud bill spiralling out of control
You pay only for what is used, with a cap and spending alerts. Reviewing that cost is part of the maintenance.
- Depending on us or on a single person
Everything is written and documented. You can host it in a cloud account owned by your company and continue with another provider.
- A third-party component having a security flaw
Every change is automatically reviewed before it is published. If a component has a known flaw, it is detected and publishing stops.
A related case
Frequently asked questions
It depends on what it needs to do. After the first meeting, we give you a plan with parts and dates. We prefer to deliver working parts rather than keep you waiting for months.
Yours. The code, the configuration and the documentation are delivered in your name. You can host it in a cloud account owned by your company.
With a meeting to understand what you need. Then we send you the quote, fixed and split into parts. We don't quote without having understood the problem.
Yes. We review it and propose moving it to the cloud in parts, without stopping what is already running. If the goal is to modernise it entirely, we have a service for that.