<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Connascent Blog</title><description>Notes from the people who build and run websites, software and school platforms: what we make, how we host it, and what we learn looking after it.</description><link>https://connascent.com.au/</link><language>en-au</language><lastBuildDate>Thu, 20 Aug 2026 00:00:00 GMT</lastBuildDate><atom:link href="https://connascent.com.au/blog/rss.xml" rel="self" type="application/rss+xml"/><item><title>EasyEntry, event ticketing we built and run</title><link>https://connascent.com.au/blog/easyentry/</link><guid isPermaLink="true">https://connascent.com.au/blog/easyentry/</guid><description>EasyEntry is an Australian event ticketing platform we built and launched. What it does, how it is built, and why we run it ourselves.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;&lt;a href=&quot;https://easyentry.com.au&quot;&gt;EasyEntry&lt;/a&gt; is an event ticketing and registration platform for Australian organisers, from club fundraisers to conferences. We built it, we launched it in August 2026, and we run it.&lt;/p&gt;
&lt;h2 id=&quot;what-it-does&quot;&gt;What it does&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Tickets and seating.&lt;/strong&gt; General admission and reserved seating, registration forms and promo codes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Check-in.&lt;/strong&gt; QR check-in runs in a browser, so there is no app to install and no hardware to buy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Teams and data.&lt;/strong&gt; Team roles, and exports as CSV or JSON.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Integration.&lt;/strong&gt; Embeds and a public API, so it fits into a site you already have.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Payments.&lt;/strong&gt; Organisers connect their own Stripe account to receive money from paid sales.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;how-it-is-built&quot;&gt;How it is built&lt;/h2&gt;
&lt;p&gt;The public site, the organiser console, the API and the staff admin are separate services sharing one PostgreSQL database, each with its own least-privilege access. It is Python and Django with HTMX and Alpine.js, hosted on AWS in Sydney.&lt;/p&gt;
&lt;h2 id=&quot;why-we-run-it-ourselves&quot;&gt;Why we run it ourselves&lt;/h2&gt;
&lt;p&gt;Ticketing has to work on the day. Running a product that people pay to use, with real events depending on it, keeps us honest about reliability. If you need custom software for a process of your own, &lt;a href=&quot;https://connascent.com.au/services/custom-software/&quot;&gt;we can build it&lt;/a&gt;.&lt;/p&gt;
</content:encoded><category>easyentry</category><category>custom-software</category></item><item><title>RedPennon, feature flags we built and run</title><link>https://connascent.com.au/blog/redpennon/</link><guid isPermaLink="true">https://connascent.com.au/blog/redpennon/</guid><description>RedPennon is a hosted feature flag service we built and launched. What it does, how it is built, and why we run it ourselves.</description><pubDate>Sat, 13 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;&lt;a href=&quot;https://redpennon.dev&quot;&gt;RedPennon&lt;/a&gt; is a hosted feature flag service. Software teams use it to turn features on and off, roll them out to some users first, and run experiments, without shipping new code each time.&lt;/p&gt;
&lt;p&gt;We built it, we launched it in June 2026, and we run it.&lt;/p&gt;
&lt;h2 id=&quot;what-it-does&quot;&gt;What it does&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Targeting.&lt;/strong&gt; Ordered rules by user ID, email, IP or a reusable audience, including percentage rollouts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Environments.&lt;/strong&gt; Development, testing and production each have their own API key and their own values.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Safe defaults.&lt;/strong&gt; A new flag is never on in production until someone turns it on.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Code references.&lt;/strong&gt; A command-line tool scans a repository in CI and shows where each flag is used, so stale flags can be found and removed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Audit trail and roles.&lt;/strong&gt; Changes to flags and rules are recorded with who made them, and production has guards.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clients.&lt;/strong&gt; Official SDKs for Node, Go and Python share one REST API, and plain HTTP works with any stack.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;how-it-is-built&quot;&gt;How it is built&lt;/h2&gt;
&lt;p&gt;The application is Python and Django, with HTMX and Alpine.js on the front end and PostgreSQL behind it. The flag evaluation API is a separate service, kept small so it can be fast. It is designed for a 95th-percentile response under 50 milliseconds. The product runs on AWS in Sydney.&lt;/p&gt;
&lt;h2 id=&quot;why-we-run-it-ourselves&quot;&gt;Why we run it ourselves&lt;/h2&gt;
&lt;p&gt;It is a real application with real customers, built the way we build for clients: scoped around the problem, tested, hosted and looked after by the same people. If you need custom software to run a process in your business, &lt;a href=&quot;https://connascent.com.au/services/custom-software/&quot;&gt;that is what we do&lt;/a&gt;.&lt;/p&gt;
</content:encoded><category>redpennon</category><category>custom-software</category></item><item><title>Hello, world: Connascent opens</title><link>https://connascent.com.au/blog/hello-world/</link><guid isPermaLink="true">https://connascent.com.au/blog/hello-world/</guid><description>Connascent Web Services started in January 2018. Who we are, what we build, and why the people who build it are the people who look after it.</description><pubDate>Fri, 12 Jan 2018 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Connascent Web Services started in January 2018, and this is where we will write about the work.&lt;/p&gt;
&lt;p&gt;Connascent means born together. We build websites and the software behind them for Australian organisations, and then we look after what we build. The build and the ongoing care are one piece of work, not a project handed over and forgotten.&lt;/p&gt;
&lt;h2 id=&quot;how-we-work&quot;&gt;How we work&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Small and in-house.&lt;/strong&gt; Whoever quotes your work is whoever does it. There is no account manager in between.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Quoted, not packaged.&lt;/strong&gt; Every project is different, so we scope it with you and say plainly what is included.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Looked after.&lt;/strong&gt; A site we make is one we keep running.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you have something in mind, &lt;a href=&quot;https://connascent.com.au/contact/&quot;&gt;tell us about it&lt;/a&gt;.&lt;/p&gt;
</content:encoded><category>connascent</category></item></channel></rss>