Revin puts its own engineering team at the service of parishes, ministries, movements and charities of the Roman Catholic Church. You bring the need and the infrastructure. We bring the work.
Apply for my communityApplications are open. We take on a few projects at a time so each one gets real attention.
Revin is a software engineering company. Many of us grew up in a parish, a youth group or a ministry, and we know how much depends on a website that works, a spreadsheet only one person understands, or a sign-up sheet kept in a notebook.
Catholic communities rarely have a budget for software development. What they do have is willing people and concrete problems. This program exists to connect the two: our team builds and deploys, the community uses.
This is not a product trial or a sales funnel. It is volunteer work run like professional work: with a scope, a timeline and a delivery.
Development and deployment work. Any technology solution the community needs that a small team can deliver in a few weeks.
Parish website, event page, retreat registration, Mass schedule. Built from scratch or rebuilt.
Simple mobile or web apps: parishioner records, ministry rosters, giving, announcements.
Routines done by hand today: spreadsheets, emails, WhatsApp reminders, reports.
Connecting tools that do not talk to each other, or building a small system for one specific need.
We put it live on the organization’s own infrastructure, configure it and hand it over working.
A session with the people who will use it every day, plus a short guide to keep.
So there are no surprises: Revin contributes work, not money. Anything paid to third parties stays with the organization.
The web address (stmaryparish.org, for example) is registered and paid for by the organization.
Where the website or system runs. We suggest options, including free ones where they exist, but the bill is the organization’s.
Email tools, payment gateways, APIs, software plans. Any subscription belongs to the organization.
Computers, phones, routers, internet connection and anything else physical.
Photographer, brand designer, printing, any professional outside our team.
After handover, the system belongs to the community. The FAQ explains how maintenance works.
Two things. Both are simple, and both matter for the program to keep going.
At the end, we ask the community to share how the experience went on the review platforms where Revin has a profile. Google, Clutch, G2 and GoodFirms are some examples; we agree at handover on which ones. The words are yours: Revin does not edit, suggest phrasing or ask for a rating. Some platforms, such as Clutch, may run a short verification interview, about 15 minutes.
On the delivered website, a "Built by Revin" line linking to revin.com.br in the footer. Discreet, matching the site’s design.
We do not ask for exclusivity, we do not ask for parishioner data, and we do not ask the community to refer Revin to anyone.
Six steps, from application to review. Nothing starts before you approve the scope in writing.
Fill in the form on this page. It takes about five minutes. Describe the need in your own words; no technical terms required.
We answer every application. Because we select in cycles, the first contact can take up to 30 days. When your turn comes, we set up a 30 to 45 minute call, by video or phone, with whoever knows the problem best.
We write a one-page scope: what will be built, what is out, what the organization needs to provide (domain, hosting, access) and the estimated timeline. You approve it before any work starts.
Our team builds, with one point of contact from the community following along. We show progress every week or two.
We deploy on the organization’s infrastructure, run the training session and hand over access and source code.
Within the following two weeks, the community publishes its review on the agreed platforms, and the credit stays in the footer. That closes the cycle.
Entities of the Roman Catholic Church, in communion with the Holy See: parishes, chapels and communities; parish or diocesan ministries and services; movements and new communities recognized by the Church; charities, schools and shelters run by one of these entities. In Brazil or anywhere else.
The program is exclusive to the Roman Catholic Church. Churches and communities that use the name "Catholic" without being in communion with Rome, and communities of other denominations, are not served here. We put this in writing so nobody is put in an awkward position later.
The application must come from someone authorized to speak for the organization: the pastor, a coordinator, an administrator or a person they appoint.
We receive more requests than we can take on at once, so we select in cycles. What counts:
We do not look at the size of the community, the city or the diocese. A rural chapel with a clear problem has the same chance as a cathedral parish.
If your question is not here, ask it in the form. We answer everything.
It depends on the scope. Most projects we accept take between three and eight weeks of development, counted from scope approval. The estimated timeline is written into the scope document before we start.
Revin’s work costs nothing. The organization pays only what it would pay third parties anyway: the domain (around US$ 15 a year), hosting (from zero to a few dollars a month, depending on the project) and any paid services the project requires. All of it is listed in the scope before we start.
Nothing happens to what was delivered: the website or system stays live and stays yours. But the program depends on these reviews to keep existing, so we treat it as a commitment. If the community would rather not review publicly, it is better not to apply.
No. We ask that it be truthful, and that is all. If something went badly, say so. We would rather have an honest review with criticism than an arranged one.
Sites like Clutch, G2 and GoodFirms review technology companies and verify that reviews are real. To do that, their team may call or send a form to confirm the project happened and that the reviewer is who they say they are. It takes about 15 minutes and can be done in English or Portuguese.
We hand over a working system with documentation and training, and stay available for 30 days to fix defects in what was delivered. After that, maintenance belongs to the community, which can handle it in-house, with a volunteer, or come back to us in a future cycle. We do not sell maintenance plans within this program.
The organization does. We hand over the source code under an open license (MIT), with no lock-in or dependency on Revin. You can change it, hire someone else to change it, or publish it. The only request is to keep the credit in the website footer.
No. The program is for entities of the Roman Catholic Church, in communion with the Pope. Communities of other churches that use the name Catholic, or of other Christian denominations, are not served by this program. We confirm the link with the parish or the diocese before approving the scope.
No. We need someone who knows the community’s routine and has time to talk and test. The technical side is ours.
No. Data stays on the organization’s infrastructure, and Revin only accesses what is needed during development, with authorization. After handover, Revin’s access is removed.
Yes. The team works in English and Portuguese, and the first conversation happens over video.
Take your time. Describe the need the way it shows up day to day; we will figure out the technical side together.